Re: sni hostname and request Host header mismatch

2018-10-10 Thread Frank Liu
http://hg.nginx.org/nginx/rev/4fbef397c753 indicates the check is only done for the 2-way SSL virtual host. Has everything been added (maybe through a directive) for 1-way SSL since then? On Wed, Oct 10, 2018 at 10:33 AM itpp2012 wrote: > Via map and the default ? > > Posted at Nginx Forum: >

Re: https auto redirect to specific port

2018-10-10 Thread c4rl
Wow, that's what I needed! It's so simple. Many thanks! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,281566,281568#msg-281568 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

https auto redirect to specific port

2018-10-10 Thread c4rl
Hi experts, I'm not sure if the subject is resuming correctly my question but I'll try to explain it. I have the configuration below in my server, this server has 2 vhosts: example.com and mydomain.com The first vhost needs to listen on 8080 (https) and as you can see I'm using a redirect from

Re: sni hostname and request Host header mismatch

2018-10-10 Thread itpp2012
Via map and the default ? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,281564,281565#msg-281565 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

sni hostname and request Host header mismatch

2018-10-10 Thread Frank Liu
Is there a way to configure nginx to fail the request if the client sends a sni header that doesn't match the Host header? curl -k -H "Host: virtual_host2" https://virtual_host1 ___ nginx mailing list nginx@nginx.org

Re: Allowing my web server to be aware of retries

2018-10-10 Thread Maxim Dounin
Hello! On Wed, Oct 10, 2018 at 12:16:15PM +0300, Rami Stern via nginx wrote: > > We use nginx's retry mechanism on timeout and errors, but we'd like to > > have some way (custom header \ url param) to make our web server know that > > the request its handling is actually a retry. > > > > We've

Re: Can't access OWA, OA and ActiveSync

2018-10-10 Thread Francis Daly
On Mon, Oct 08, 2018 at 11:58:38PM -0400, alisampras wrote: Hi there, I have not tried putting anything to do with Exchange behind nginx, so I do not have any tested-config for you. However... > Business Objective > Outside users (users travelling) should be able to access their email >

Allowing my web server to be aware of retries

2018-10-10 Thread Rami Stern via nginx
> We use nginx's retry mechanism on timeout and errors, but we'd like to > have some way (custom header \ url param) to make our web server know that > the request its handling is actually a retry. > > We've tried adding $proxy_add_x_forwarded_for and $upstrea_addr but the > first didn't return