You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
In my adventures, I tend to find that the use case for overriding an HTTP method comes from web browsers where we all know there is poor support for anything other than POST and GET.
I'm just wondering how useful this middleware package is when solely relying on a header to do the overriding? Generally, clients that can set headers can also make requests with deliberate HTTP methods.
Would it be possible to have this upgraded to use a POST form field, and query-string parameter alongside the header?
I like this idea. After a quick search I found other similar middlewares providing this feature, some only use the post body, others also the query string parameteres. What do you think about something like this?:
Middleware::methodOverride()
->parameter('http-method-override') //To use this parameter in the parsed body and url query
->parameter('http-method-override', false) //To use only in the parsed body
In my adventures, I tend to find that the use case for overriding an HTTP method comes from web browsers where we all know there is poor support for anything other than POST and GET.
I'm just wondering how useful this middleware package is when solely relying on a header to do the overriding? Generally, clients that can set headers can also make requests with deliberate HTTP methods.
Would it be possible to have this upgraded to use a POST form field, and query-string parameter alongside the header?
It would become so much more useful in the wild with additions like this.
The text was updated successfully, but these errors were encountered: