rop it on the floor and continue, e.g. like this
--- a/modules/proxy/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 &&
: 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
homas Eckert [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 f
]
Gesendet: Mittwoch, 27. November 2013 11:20
An: dev@httpd.apache.org
Betreff: Re: ap_proxy_location_reverse_map()
Given a config extract like
BalancerMember https://mybackend.local status=-SE
...
ProxyPass balancer://abcd/
ProxyPassReverse balancer://abcd/
what exactly is your suggestion
iger
>
>
>
> *Von:* Thomas Eckert [mailto:thomas.r.w.eck...@gmail.com]
> *Gesendet:* Mittwoch, 27. November 2013 11:20
> *An:* dev@httpd.apache.org
> *Betreff:* Re: ap_proxy_location_reverse_map()
>
>
>
> Given a config extract like
>
>
>
>
>
> BalancerMe
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
BalancerMember https://mybackend.local status=-SE
Balancer
: 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
>
>
>
> ProxyPassReverse / https://mybackend.local
>
> ProxyPassReverse / https://mybackend.local:443
>
>
>
> Regards
>
>
>
> Rüdiger
>
>
>
> Von: Thomas Eckert [mailto:thomas.r.w.eck...@gmail.com]
> Gesendet: Mittwoc
er
>
>
>
> *Von:* Plüm, Rüdiger, Vodafone Group
> *Gesendet:* Mittwoch, 27. November 2013 12:19
> *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
>
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
s
>
> Rüdiger
>
>
>
>
>
> *Von:* Thomas 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
>
>
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 translate this into a
configuration like the extract 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
13 matches
Mail list logo
