Open amoghyermalkar123 opened 2 years ago
map https://example.com/ https://example.com/
dest_domain=. method=get parent="127.0.0.1:8000" scheme=http
The scheme on the parent.config line needs to match the scheme of the remap target, not the source. The remap target here is https
, so the parent.config line needs to be scheme=https
to match.
This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.
map https://example.com/ https://example.com/
dest_domain=. method=get parent="127.0.0.1:8000" scheme=http
The scheme on the parent.config line needs to match the scheme of the remap target, not the source. The remap target here is
https
, so the parent.config line needs to bescheme=https
to match.
Would be great time saver if this would be clearly stated in documentation. Documentation at https://docs.trafficserver.apache.org/admin-guide/files/parent.config.en.html only has following about the scheme.
scheme
A request URL protocol: http or https.
No reference to remap dependency, not clear what request.
Problem -
My Parent.config -
My records.config -
My remap.config -
Detailed Description of the Problem - We are using nginx as the parent server which runs on the same physical machine as ATS on port 8000. We are seeing failures where ATS tries to resolve the origin domain defined in remap.config, instead of going to the local nginx. Our expectation out of these configurations is that, remap should only be used for request transformation, we need the outbound host header as in this case is
example.com
to be served via the nginx that runs locally on port 8000.What's currently happening is that ATS does not try to reach out to the local nginx in the first place instead, it DNS resolves
example.com
and requests that machine the domain points to, bypassing the parent configuration logic completely.