[mailto:thomas.r.w.eck...@gmail.com]
*Sent:* Dienstag, 26. November 2013 17:11
*To:* dev@httpd.apache.org
*Subject:* ap_proxy_location_reverse_map()
I've been debugging some problems with incorrectly reverse mapped Location
headers and found some backend servers (e.g. OWA for Exchange 2013) to give
]
Gesendet: Mittwoch, 27. November 2013 11:20
An: dev@httpd.apache.org
Betreff: Re: ap_proxy_location_reverse_map()
Given a config extract like
Proxyy balancer://abcd
BalancerMember https://mybackend.local status=-SE
/Proxy
...
Location /
ProxyPass balancer://abcd/
ProxyPassReverse balancer://abcd
*Betreff:* Re: ap_proxy_location_reverse_map()
Given a config extract like
Proxyy balancer://abcd
BalancerMember https://mybackend.local status=-SE
/Proxy
...
Location /
ProxyPass balancer://abcd/
ProxyPassReverse balancer://abcd/
/Location
what exactly is your suggestion
Betreff: Re: ap_proxy_location_reverse_map()
Thanks but you ignored the config extract I mentioned.
ProxyPassReverse / https://mybackend.local
ProxyPassReverse / https://mybackend.local:443
does this not translate to
Proxyy balancer://abcd
BalancerMember https://mybackend.local status=-SE
: ap_proxy_location_reverse_map()
What location would you expect? I agree that the result you see is not correct.
BTW: ProxyPassReverse does not change anything to your balancer setup.
Regards
Rüdiger
Von: Thomas Eckert [mailto:thomas.r.w.eck...@gmail.com]
Gesendet: Mittwoch, 27. November 2013 11:54
An: dev
. November 2013 11:20
An: dev@httpd.apache.org
Betreff: Re: ap_proxy_location_reverse_map()
Given a config extract like
Proxyy balancer://abcd
BalancerMember https://mybackend.local status=-SE
/Proxy
...
Location /
ProxyPass balancer://abcd/
ProxyPassReverse balancer
*An:* dev@httpd.apache.org
*Betreff:* AW: ap_proxy_location_reverse_map()
What location would you expect? I agree that the result you see is not
correct.
BTW: ProxyPassReverse does not change anything to your balancer setup.
Regards
Rüdiger
*Von:* Thomas Eckert
Eckert [mailto:thomas.r.w.eck...@gmail.com]
Gesendet: Mittwoch, 27. November 2013 13:44
An: dev@httpd.apache.org
Betreff: Re: ap_proxy_location_reverse_map()
Reversing the order results in
Location https://myfrontend.local/path/path/file?query
My expectation is that
Location https
[mailto:thomas.r.w.eck...@gmail.com]
*Gesendet:* Mittwoch, 27. November 2013 13:44
*An:* dev@httpd.apache.org
*Betreff:* Re: ap_proxy_location_reverse_map()
Reversing the order results in
Location https://myfrontend.local/path/path/file?query
My expectation is that
Location https
ProxyPassReverse directives in case of such
backends.
Regards
Rüdiger
Von: Thomas Eckert [mailto:thomas.r.w.eck...@gmail.com]
Gesendet: Mittwoch, 27. November 2013 14:42
An: dev@httpd.apache.org
Betreff: Re: ap_proxy_location_reverse_map()
Indeed, with that example it works. Now how do I
Hi,
Am 27.11.2013 12:54, schrieb Jim Jagielski:
[...] I'm guessing that if we
standardized on using apr_uri_parse() instead of just
trying to parse the stuff ourselves, we'd be better off.
+1
Regards,
Micha
/proxy_util.c
+++ b/modules/proxy/proxy_util.c
@@ -894,11 +894,17 @@ PROXY_DECLARE(const char *)
ap_proxy_location_reverse_map(request_rec *r,
}
}
else if (l1 = l2 strncasecmp((*worker)-s-name, url,
l2) == 0) {
+const char* tmp_pchar
: ap_proxy_location_reverse_map()
I've been debugging some problems with incorrectly reverse mapped Location
headers and found some backend servers (e.g. OWA for Exchange 2013) to give
headers like
Location: https://myserver:443/path/file?query
which I think are perfectly fine. mod proxy fails to do the trick
13 matches
Mail list logo