Hi, Many thanks for the reply. Outputs below... (ive also included a CURL direct to origin, www.xyz.com which seems to be a 301 as well. Could this be confusing things?).
A little more info, I tried on my works network and the target (www.abc.com/c) remains (as expected, www.abc.com/c/) using chrome browser but when trying on my phone or home network, the origin (www.xzy/c/) is shown instead (chrome browser as well). Its like we have different calling systems either following the 301 or ignoring the 301? *------ $ curl -IX GET -x 127.0.0.1:80 http://www.abc.com/c HTTP/1.1 301 Moved Permanently Server: ATS/7.1.3 Date: Thu, 19 Jul 2018 11:22:23 GMT Content-Type: text/html Content-Length: 178 Location: http://www.abc.com/c/ Age: 0 Proxy-connection: keep-alive *------ $ curl -IX GET http://www.abc.com/c HTTP/1.1 301 Moved Permanently Server: ATS/7.1.3 Date: Thu, 19 Jul 2018 11:25:42 GMT Content-Type: text/html Content-Length: 178 Location: http://www.abc.com/c/ Age: 0 Proxy-connection: keep-alive *------ $ curl -IX GET http://www.xyz.com/c HTTP/1.1 301 Moved Permanently Server: ATS/7.1.3 Date: Thu, 19 Jul 2018 11:32:16 GMT Content-Type: text/html Content-Length: 178 Location: http://www.xyz.com/c/ Age: 0 Proxy-connection: keep-alive Many thanks -- Sent from: http://apache-traffic-server.24303.n7.nabble.com/
