On Wed, Jan 11, 2017 at 1:07 PM, Willy Tarreau <w...@1wt.eu> wrote: > This one is obsolete, the format of the Location header field is > described here : > > https://tools.ietf.org/html/rfc7231#page-68 > > and it uses this format : > > https://tools.ietf.org/html/rfc3986#section-4.2 > > As you can see, "//" authority path, path-absolute etc... are permitted. > > However while I understand it could solve your issue, I think it's an > ugly trick in that you use it only to work around an undesirable haproxy > behaviour. We'd rather ensure haproxy doesn't behave this way if not > needed. Of course it could be a short-term workaround saving your from > modifying the code.
Quick reply: this would work only if we assume that we want to keep the traffic on the same "transport", namely TLS or non-TLS. But these days, when TLS is starting to become widely deployed, I assume most redirects are on the form of `https://canonical-domain.com`. Ciprian.
