Re: Proxy domain rewrite using proxy_cookie_domain

Thanks for reply. In case client is just a browser then it will send all the cookies with NGIX domain which means that NGIX will send all the cookies to backend server irrespective of who initially set it in set-cookie header.. This could be a security issue then. Posted at Nginx Forum: https://f

Re: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

As you're using a 'privileged' port ( ie one with a value lower than approx 1000 ), the process needs to be run by a superuser. You can set it up through sudo to reduce the risk for an ordinary user. On 02/13/2016 07:22 AM, smsmaddy1981 wrote: Any other feasibility to achieve restart of Nginx

Re: proxy_pass not seen as SNI-client according to Apache directive

Hello! On Sun, Feb 14, 2016 at 01:46:48PM -0800, Robert Paprocki wrote: > > On Feb 14, 2016, at 12:58, Maxim Dounin wrote: > > > > Hello! > > > >> On Sun, Feb 14, 2016 at 08:14:20PM +0100, Lucas Rolff wrote: > >> > >> I'm having a rather odd behavior - I use nginx as a reverse proxy > >> (ba

Re: proxy_pass not seen as SNI-client according to Apache directive

Hi Maxim, Thank you a lot for the quick reply, I'll give it a test tomorrow morning! And Robert has a valid point indeed, why is it actually disabled by default? Robert Paprocki 14 February 2016 at 22:46 Out of curiosity, is there a philosophical

Re: proxy_pass not seen as SNI-client according to Apache directive

> On Feb 14, 2016, at 12:58, Maxim Dounin wrote: > > Hello! > >> On Sun, Feb 14, 2016 at 08:14:20PM +0100, Lucas Rolff wrote: >> >> I'm having a rather odd behavior - I use nginx as a reverse proxy (basically >> as a CDN) - where if the file isn't in cache, I do use proxy_pass to the >> origi

Re: proxy_pass not seen as SNI-client according to Apache directive

Hello! On Sun, Feb 14, 2016 at 08:14:20PM +0100, Lucas Rolff wrote: > I'm having a rather odd behavior - I use nginx as a reverse proxy (basically > as a CDN) - where if the file isn't in cache, I do use proxy_pass to the > origin server, to get the file and then cache it. > > This works perfect

proxy_pass not seen as SNI-client according to Apache directive

Hi guys, I'm having a rather odd behavior - I use nginx as a reverse proxy (basically as a CDN) - where if the file isn't in cache, I do use proxy_pass to the origin server, to get the file and then cache it. This works perfectly in most cases, but if the origin is running apache and happen

Re: Nginx as proxy for Exchange 2013 : RPC?

I've had most success so far with this approach (Tigunov's config - https://gist.github.com/taddev/7275873). ( btw, I'm using Basic Authentication rather than NTLM ). server { server_name mail.contoso.com; server_name autodiscover.contoso.com; keepalive_timeout 3h; proxy_read_timeout 3h; #reset_