As modern frontend frameworks grow more and more complex, there is an alarming rise in the number of the so-called client-side redirects. Nginx has a great facility that will allow you to save some traffic and precious client waiting time on client redirects. First, let us briefly refresh your knowledge of those redirects.
All the HTTP responses are documents consisting of three principal parts:
There's the HTTP code (200: Ok, 404: Not found, and so on)
There are a number of loosely structured key-value pairs in the form of headers
There is a relatively large, opaque, optional body
There is a lot of good HTTP response codes documentation on the Internet (and also some hilarious pieces given at http://httpstatusdogs.com/)—the ones that are relevant to our discussion are in the fourth hundred, that is, between 300 and 399.
Responses with those codes are indications that a browser should immediately make another request instead of the original one....