bryancall commented on issue #12048:
URL:
https://github.com/apache/trafficserver/issues/12048#issuecomment-4828270775
I am closing this out as a configuration question rather than a Traffic
Server defect. The behavior you are seeing, where the origin (IHS) host appears
instead of your Traffic Server fully qualified domain name, is controlled
behavior, and the mechanisms to get what you want all still exist in current
Traffic Server. As mlibbey noted, two settings cover this: act at remap time in
header_rewrite with `cond %{REMAP_PSEUDO_HOOK}`, and use
[proxy.config.url_remap.pristine_host_hdr](https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.yaml.en.html#proxy-config-url-remap-pristine-host-hdr)
to choose whether the inbound or the remapped host header is sent to origin.
The remaining piece, your authentication server emitting the redirect uniform
resource identifier with the IHS hostname, is a function of how that auth
server is configured rather than Traffic Server, since it derives the redirect
from the request it actually receives. There is no open code defect to trac
k here, so I am closing this. If you can reproduce a case where Traffic Server
itself rewrites a value it should not, please open a fresh issue with your full
remap.config, header_rewrite configuration, and a request and response capture,
and we will take another look.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
