lapis icon indicating copy to clipboard operation
lapis copied to clipboard

Support for custom HTTP methods

Open ahmadnassri opened this issue 9 years ago • 9 comments

currently it takes quite a considerable effort to create work-arounds to support HTTP methods such as PATCH, which behavior shouldn't really differ from POST (or any other method for that matter)

is there a reason for the core to be opinionated such as it is today? even with things like request bodies coupling with the HTTP Method behavior?

as far as the HTTP Spec goes, there is no limit to what HTTP Method strings can be/ (GET, POST, etc ...) being the common ones, and there is certainly no requirement nor association with HTTP Methods and request bodies beyond tradition.

will there be future plans to allow free-form HTTP method usage and decoupling the HTTP Method parsing from any further actions within the app?

if nothing else, then at the very least adopt the IANA Registery of HTTP Methods.

ahmadnassri avatar May 14 '15 21:05 ahmadnassri