> RewriteRule ^/2/(.*)$ https://my_reverse_proxy/rp/1/2/$1
>
> So:
> 1) why do I need to specify an absolute URL?
> 2) is there a variable name I could use instead of my_reverse_proxy?
To answer 2) myself: %{SERVER_NAME}.
I still haven't figured out 1) though.
On Tue, Jan 14, 2020 at 12:05 PM Vieri Di Paola wrote:
> The client browser tries to connect to
>
> https://my_apache_reverse_proxy/2/css/bootstrap.12pt.css
>
> instead of
>
> https://my_apache_reverse_proxy/rp/1/2/css/bootstrap.12pt.css (typo corrected)
> or
> https://my_apache_reverse_proxy/pr/
On Tue, Jan 14, 2020 at 11:48 AM Colin 't Hart wrote:
>
> Looks like you have a transposition typo in your rewrite rule.
Thanks for seeing that typo. I fixed it, but in any case that wasn't
it because there is no match on that rewrite rule.
The client browser tries to connect to
https://my_apac
Looks like you have a transposition typo in your rewrite rule.
/Colin
On Tue, 14 Jan 2020 at 11:42, Vieri Di Paola wrote:
> Hi,
>
> I can successfully access a backend server through directives like these:
>
> ProxyPass / http://192.168.250.1:8080/
> ProxyPassReverse / http://19
Hi,
I can successfully access a backend server through directives like these:
ProxyPass / http://192.168.250.1:8080/
ProxyPassReverse / http://192.168.250.1:8080/
However, I'm having trouble if I use this other configuration:
ProxyPass /rp/1/ http://192.168.250.1:8080/
