Add support for X-HTTP-Method-Override header on REST requests #814
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes a client cannot consume REST services using methods like PUT, DELETE or PATCH, due to browser limitation or firewall rules. Some frameworks provide a workaround using the X-HTTP-Method-Override header to override the method of a request. No change to the route configuration is necessary. The client of the API just informs the override header, and the ERRest library maps routes as expected. Keeping a RESTful API on the server side is the main benefit of that approach. No need for alternate / unRESTfull routes creation.
Scott Hanselman talked in more detail about that in a blog post.