Remove special handling of the HTTP Location header

[kanongil]

When reply.redirect() is called with a relative url, the resulting Location header is currently mapped to an absolute url. When coupled with a reverse proxy the hapi logic can result in an incorrect Location header.

Since the proposed https://tools.ietf.org/html/rfc7231#section-7.1.2 allows relative URI references and most agents seem to already support it, would it be possible to disable this rewriting somehow?

[kanongil]

I guess this request is somewhat related to the issue behind #1747.

[hueniverse]

Given the change in the HTTP 1.1 specification, I no longer see why we need to prefix locations at all. This is a relic from an early version of postmile when HTTP still required absolute URIs. The new specification doesn't even mention this old requirement anymore and all modern browsers support relative locations.

This code has been a huge pain in the ass so will gladly get rid of this crap and let people who want absolute URIs deal with them as they see fit with whatever rules they want. I am sure someone can write a fancy plugin that does this based on some fancy logic.

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.