<div dir="ltr">Hi Francis Daly,<div><br></div><div>client -> reverse proxy: <a href="https://myreverseproxy.com/https://mypub/somepath" rel="noreferrer" target="_blank">https://myreverseproxy.com/https://mypub/somepath</a> </div><div>reverse proxy to forward proxy: I'm not sure how <a href="https://forwardproxy.com/">https://forwardproxy.com/</a><a href="https://myreverseproxy.com/https://mypub/somepath" rel="noreferrer" target="_blank">https://mypub/somepath</a></div><div><br></div><div>I was trying to append the actual url into the reverse proxy so in its config we can easily user $request_uri and pass it along and may be thinking that is what you meant by "http through proxy" and forward proxy will be able to interpret and do needful.  like you said some forward proxy will be able to do it and if so then above looks good to me.</div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 27, 2023 at 1:18 PM Francis Daly <<a href="mailto:francis@daoine.org">francis@daoine.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, May 26, 2023 at 04:18:59PM +0530, Miten Mehta wrote:<br>
<br>
Hi there,<br>
<br>
> Thanks for guidance.  If i enable direct internet access from reverse proxy<br>
> then can i just use proxy_pass $request_uri and have user format his url as<br>
> <a href="https://myreverseproxy.com/https://mypub/somepath" rel="noreferrer" target="_blank">https://myreverseproxy.com/https://mypub/somepath</a>.<br>
<br>
Here, $request_uri would start with /, so it would not Just Work as-is.<br>
<br>
I'm not sure how <a href="https://myreverseproxy.com/https://mypub/somepath" rel="noreferrer" target="_blank">https://myreverseproxy.com/https://mypub/somepath</a> is<br>
different from a "normal" <a href="https://myreverseproxy.com/mypub/somepath" rel="noreferrer" target="_blank">https://myreverseproxy.com/mypub/somepath</a><br>
with a "normal" nginx config based on<br>
<br>
        location ^~ /mypub/ { proxy_pass <a href="https://mypub/" rel="noreferrer" target="_blank">https://mypub/</a>; }<br>
<br>
(plus the supporting configuration). So then you have a "normal" nginx<br>
proxy_pass setup for specific remote web servers.<br>
<br>
Which should Just Work like any other proxy_pass configuration.<br>
<br>
Good luck with it,<br>
<br>
        f<br>
-- <br>
Francis Daly        <a href="mailto:francis@daoine.org" target="_blank">francis@daoine.org</a><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="https://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">https://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div>