We have noticed that when using nginx internal 301 and 302 handling, nginx will serve a small document body with the appropriate Location: … header.
Something along the lines of (in html): 301 redirect – nginx.
As appropriate in the above behaviour, a content-type text/html and content-length header is also sent.
We do a lot of 302 and some 301 redirects, the above behaviour is wasted bandwidth in our opinion.
Any way to disable this behaviour?
One idea that crossed our mind was to set error_page 301 302 to an empty text file. We have not tested this yet, but I am assuming even with the above, the content-type and content-length (0) headers will be sent.
So, is there a clean way to send a “body-less” 301/302 redirect with nginx?
Think very carefully about what you’re asking for, and strongly consider not doing it.
RFC 2616 specifies that the entity bodies you want to remove should be present.
10.3.2 301 Moved Permanently
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
10.3.3 302 Found
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
SHOULD, in this context, is defined in RFC 2119:
This word, or the adjective “RECOMMENDED”, mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
Now you can do this without violating the RFC, but you should be aware of the full implications:
- You are doing a lot of work for virtually no benefit. The only logical reason I can think of to disable the entity body is to save on bandwidth costs, and indeed this is the reason you mentioned, but the difference is so minimal that it’s unlikely you’ll even see a difference on your bandwidth graphs.
- A very tiny fraction of web clients don’t automatically follow 3xx redirects. This fraction was much larger when the RFC was written, which is why this is there in the first place, but there are still ancient monstrosities lurking in the shadows of dark bedrooms and data center closets, and sometimes they come out to play. The one you are most likely to see is
curl, which is still in common use.
This recommendation has been relaxed somewhat with RFC 7231, which merely says (for both 301 and 302):
The server’s response payload usually contains a short hypertext note with a hyperlink to the new URI(s).
The server’s response payload usually contains a short hypertext note with a hyperlink to the different URI(s).
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.