brbzull0 edited a comment on issue #2742: URL: https://github.com/apache/trafficserver/issues/2742#issuecomment-847117843
I've put together a [unit tests](https://github.com/apache/trafficserver/commit/79524ffd279e07eb2185ee051c63ab38f548cc4f) which does what's described in this issue. _Notes: I've used `foo.test/ping & bar.test/pong` instead of `foo.test & bar.test` for this test_ curl output: ``` > GET http://foo.test/ping HTTP/1.1 > Host: foo.test > User-Agent: curl/7.69.1 > Accept: */* > Proxy-Connection: Keep-Alive > uuid: issue2742 > ... < HTTP/1.1 302 Redirect < location: /kau < Date: Mon, 24 May 2021 15:00:54 GMT < Age: 0 < Transfer-Encoding: chunked < Proxy-Connection: keep-alive < Server: ATS/10.0.0 < ... * Issue another request to this URL: 'http://foo.test/kau' ... > GET http://foo.test/kau HTTP/1.1 > Host: foo.test > User-Agent: curl/7.69.1 > Accept: */* > Proxy-Connection: Keep-Alive > uuid: issue2742 > .... < HTTP/1.1 200 OK < host: foo.test < Date: Mon, 24 May 2021 15:00:54 GMT < Age: 0 < Transfer-Encoding: chunked < Proxy-Connection: keep-alive < Server: ATS/10.0.0 < ``` I had a look at [this](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/http/http_connection_management#internal-redirects) and it seems they expect the `Location` to be a fully qualified url in cases like this(haven't tried that though) Should ATS enforce the `Location` to some format? I think we need to discuss how to proceed with this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
