NGN.NET Redirect Cache

[coreybutler]

When web requests receive a redirect response (301, 302, etc), either to another domain or another endpoint, the endpoint should be cached for future use. In other words:

1. Request https://mydomain.com/path/to/content returns a 301 (permanent redirect) to https://someotherplace.com, which returns a 302 or 307 (moved temporarily) to https://finaldestination.com.
2. Hash map stores https://mydomain.com/path/to/content --> https://someotherplace.com because that is the known permanent redirect. Anytime a user requests https://mydomain.com, NGN.NET should instead request https://someotherplace.com, which will reduce the route by a single hop.

Typically, the browser will prevent itself from making too many redirected requests.

Does the browser auto-resolve domain redirects? Is this functionality even necessary?