Grails: Overriding the HTTP Method

gitSome browsers, clients, networks, firefwalls, etc. don’t allow HTTP methods beyond GET and POST.  With Grails you can get around this by POSTing an additional parameter ‘_method‘ which will be used to override the request’s HTTP Method/Verb.

If you post with an additional Parameter of ‘_method‘ (or the X-HTTP-Method-Override header if the ‘_method‘ parameter isn’t present) Grails will internally route it correctly using the value of that parameter (or header).  This is helpful when doing RESTful services or clean URLs that map to HTTP methods.

This is helpful if you are using a client that restricts HTTP verbs like Flex used to (still does?) or other browsers.  In fact the <g:form> tag will add the extra _method parameter for you if you use a method other than GET or POST.  This is something to keep in mind when doing Ajax or using alternative clients.

Hidden in chapter 13 of the documentation is one paragraph about this:

<g:form controller="book" method="DELETE">
  ...
</g:form>

Grails will send a hidden parameter called _method, which will be used as the request’s HTTP method. Another alternative for changing the method for non-browser clients is to use the X-HTTP-Method-Override to specify the alternative method name.

About the Author

Object Partners profile.

One thought on “Grails: Overriding the HTTP Method

  1. Pingback: » Blog Archive
Leave a Reply

Your email address will not be published. Required fields are marked *

Related Blog Posts
An Exploration in Rust: Musings From a Java/C++ Developer
Why Rust? It’s fast (runtime performance) It’s small (binary size) It’s safe (no memory leaks) It’s modern (build system, language features, etc) When Is It Worth It? Embedded systems (where it is implied that interpreted […]
Getting Started with CSS Container Queries
For as long as I’ve been working full-time on the front-end, I’ve heard about the promise of container queries and their potential to solve the majority of our responsive web design needs. And, for as […]
Simple improvements to making decisions in teams
Software development teams need to make a lot of decisions. Functional requirements, non-functional requirements, user experience, API contracts, tech stack, architecture, database schemas, cloud providers, deployment strategy, test strategy, security, and the list goes on. […]
JavaScript Bundle Optimization – Polyfills
If you are lucky enough to only support a small subset of browsers (for example, you are targeting a controlled set of users), feel free to move along. However, if your website is open to […]