Hmmm... that's not really an option. The upstream does not know that it's
under a subdir of the domain (and the devs insist that it shouldn't be
coupled to that).

Also, if the cookie detection lines are commented out, the proxy_pass (w/
the ending forward slash) works as expected.

This specific behavior (cookie detection affecting proxy_pass) seems rather
inconsistent. =/

Other than that the requirements are similar to the thread named "Rewriting
location directive by upstream servers".

Thanks :D

*Marcello Rocha*
Pesquisa & Desenvolvimento


Date: Fri, 26 Sep 2014 14:11:57 -0300
> From: Wandenberg Peixoto <wandenberg@gmail.com>
> To: nginx@nginx.org
> Subject: Re: Weird behavior when checking the existence of a cookie
> Message-ID:
> <
> CAFXmt0Uvo1oQnFvvDBRHZNV8cG5+MqWDig3qBUAzFR+BkeNtYg@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> By default the $uri is appended to the proxy_pass directive.
> Since you defined as
> proxy_pass http://upstream*/*;
> and the $uri starts with a slash you will have a double slash.
>
> Try to set proxy_pass like
> proxy_pass http://upstream;
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx