IMHO this should be fixed in the configuration with an additional mapping that
has the port in. In many cases the port matters.
Regards
Rüdiger
From: Thomas Eckert [mailto:thomas.r.w.eck...@gmail.com]
Sent: Dienstag, 26. November 2013 17:11
To: dev@httpd.apache.org
Subject: ap_proxy_location_re
Given a config extract like
BalancerMember https://mybackend.local status=-SE
...
ProxyPass balancer://abcd/
ProxyPassReverse balancer://abcd/
what exactly is your suggestion ? Also, can you give an example for a
situation where the port matters ?
On Tue, Nov 26, 2013 at 5:14 PM, Plüm
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
>
>
>
> ProxyPassReverse / https://mybackend.local
>
> ProxyPassReverse / https://mybackend.local:443
>
>
>
> Regards
>
>
>
> Rüdiger
>
>
>
> Von: Thomas Eckert [mailto:thomas.r.w.eck...@gmail.com]
> Gesendet: Mittwoc
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:* d
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
>
>
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
