On Mon, May 21, 2018 at 01:57:07PM +, Mik J via nginx wrote:
Hi there,
> I would like to know what is the best practice to setup a web proxy.
>
> I do it like this
> - 1 virtual host per application on the reverse proxy and the proxy_pass
> points to one IP+path
> - 1 virtual host
Hello,
Sorry if I'm asking again a question on the same topic.
I would like to know what is the best practice to setup a web proxy.
I do it like this
- 1 virtual host per application on the reverse proxy and the proxy_pass points
to one IP+path
- 1 virtual host (default) for all application
On Sun, Aug 27, 2017 at 11:27:05AM +, Mik J via nginx wrote:
Hi there,
> > Thats because the pages are called by the reverse proxy server
> > like http://10.1.1.10:80/app/application1/;and it can't use a FQDN
> > because it's in a private adressing
> Francis: I don't follow that last part.=>
Hello Francis,
Thank you for your answer.I've done many tests since then and yes indeed the
problem came from the application => wordpress
It's necessary to define these two variables WP_HOME and WP_SITEURL or
$_SERVER['HTTP_HOST'] = $_SERVER['HTTP_X_FORWARDED_HOST'] in wp-config.php
>From that
On Fri, Aug 18, 2017 at 07:01:26AM +, Mik J via nginx wrote:
Hi there,
> What would you do if you had ?
> CLIENT <-> INTERNET <->Reverse_Proxy<->Web_Server
That is the normal case, is it not? So just "use nginx as normal".
> On de web server I just use one default virtual host with
On Thu, Aug 10, 2017 at 09:17:14PM +, Mik J via nginx wrote:
Hi there,
> I have application1.org and application2.org.
>
> The client requesting these URLs, arrives one the reverse proxy.
>
> On this reverse proxy I have a virtual host which looks like that
>
> server {
> server_name
