[jira] [Updated] (TS-1024) remap_required 0 not functioning in revproxy mode
[ https://issues.apache.org/jira/browse/TS-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1024: -- Assignee: Jon Sime remap_required 0 not functioning in revproxy mode - Key: TS-1024 URL: https://issues.apache.org/jira/browse/TS-1024 Project: Traffic Server Issue Type: Bug Components: Remap API Affects Versions: 3.0.2 Reporter: Greg Dallavalle Assignee: Jon Sime Priority: Minor Labels: parent, remap_required Fix For: Docs with [records.config] proxy.config.url_remap.remap_required INT 0 proxy.config.http.parent_proxy_routing_enable INT 1 proxy.config.http.no_dns_just_forward_to_parent INT 1 ATS still requires a remap URL to be used. The way I worked around this was to have remapped URLs to themselves: [remap.config] map http://example.com http://example.com map http://sub.example.com http://sub.example.com With those settings all requests are passed through to my origin, or parent cache servers. The pass to the parent cache did not work in 3.0.1. I had to build from the 3.0.x branch for this to function. [parent.config] dest_domain=. parent=1.2.3.4:80; 4.5.6.7:80 round_robin=strict I think this is convoluted given my fairly common setup of two reverse proxies caching/load balancing round robin to a few origin servers. I guess the only bug here is that the remap_required parameter is not functioning as well as it could be. I hope for improvement in the way this setup is handled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-1024) remap_required 0 not functioning in revproxy mode
[
https://issues.apache.org/jira/browse/TS-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1024:
--
Fix Version/s: (was: 3.1.3)
sometime
Moving this out to to later for now.
So, the issue here is that enabling reverse proxy sort of interferes with
the parent proxy behavior here. If you disable reverse proxy (non-intuitive),
and make sure that all requests are proxied to a parent proxy, I think it
should work. The thing is, enabling reverse proxy currently implies that some
sort of mapping should be done. So, in a pure parent proxy setup, you want
{code}
CONFIG proxy.config.http.parent_proxy_routing_enable INT 1
CONFIG proxy.config.reverse_proxy.enabled INT 0
CONFIG proxy.config.url_remap.remap_required INT 0
{code}
And then, you shouldn't need anything at all in remap.config (it's never
consulted since reverse_proxy is disabled).
You have to be pretty careful in this setup, and assure that you parent proxy
every request (otherwise, since remap isn't required, you could become an open
proxy). We have sort of overloaded too much semantics into these two
configuration options, hence, we might want to revisit it later (and redo it
completely). The way I tend to see it is that requiring (and configuring) remap
also acts as a whitelist of what requests should be proxied.
Let me know what you think.
remap_required 0 not functioning in revproxy mode
-
Key: TS-1024
URL: https://issues.apache.org/jira/browse/TS-1024
Project: Traffic Server
Issue Type: Bug
Components: Remap API
Affects Versions: 3.0.2
Reporter: Greg Dallavalle
Assignee: Leif Hedstrom
Priority: Minor
Labels: parent, remap_required
Fix For: sometime
with
[records.config]
proxy.config.url_remap.remap_required INT 0
proxy.config.http.parent_proxy_routing_enable INT 1
proxy.config.http.no_dns_just_forward_to_parent INT 1
ATS still requires a remap URL to be used. The way I worked around this was
to have remapped URLs to themselves:
[remap.config]
map http://example.com http://example.com
map http://sub.example.com http://sub.example.com
With those settings all requests are passed through to my origin, or parent
cache servers. The pass to the parent cache did not work in 3.0.1. I had
to build from the 3.0.x branch for this to function.
[parent.config]
dest_domain=. parent=1.2.3.4:80; 4.5.6.7:80 round_robin=strict
I think this is convoluted given my fairly common setup of two reverse
proxies caching/load balancing round robin to a few origin servers. I guess
the only bug here is that the remap_required parameter is not functioning
as well as it could be. I hope for improvement in the way this setup is
handled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1024) remap_required 0 not functioning in revproxy mode
[ https://issues.apache.org/jira/browse/TS-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1024: -- Fix Version/s: 3.1.2 remap_required 0 not functioning in revproxy mode - Key: TS-1024 URL: https://issues.apache.org/jira/browse/TS-1024 Project: Traffic Server Issue Type: Bug Components: Remap API Affects Versions: 3.0.2 Reporter: Greg Dallavalle Priority: Minor Labels: parent, remap_required Fix For: 3.1.2 with [records.config] proxy.config.url_remap.remap_required INT 0 proxy.config.http.parent_proxy_routing_enable INT 1 proxy.config.http.no_dns_just_forward_to_parent INT 1 ATS still requires a remap URL to be used. The way I worked around this was to have remapped URLs to themselves: [remap.config] map http://example.com http://example.com map http://sub.example.com http://sub.example.com With those settings all requests are passed through to my origin, or parent cache servers. The pass to the parent cache did not work in 3.0.1. I had to build from the 3.0.x branch for this to function. [parent.config] dest_domain=. parent=1.2.3.4:80; 4.5.6.7:80 round_robin=strict I think this is convoluted given my fairly common setup of two reverse proxies caching/load balancing round robin to a few origin servers. I guess the only bug here is that the remap_required parameter is not functioning as well as it could be. I hope for improvement in the way this setup is handled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
