Re: Redirect without and SSL certificate

2018-07-18 Thread Friscia, Michael
Thanks, I had not heard of that solution so I will chase it down to see if we can make it work. As for the response, I assumed that was the case and what’s the point of SSL if there was a way to bypass it…just wishful thinking… ___ Michael Friscia Office

Redirect without and SSL certificate

2018-07-18 Thread Friscia, Michael
We have a problem where we have a large number of vanity domain names that are redirected. For example we have surgery.yale.edu which redirects to medicine.yale.edu/surgery. This works fine until someone tries to request https://surgery.yale.edu. For administrative reasons, I cannot get a

Re: Redirect without and SSL certificate

2018-07-18 Thread Maxim Dounin
Hello! On Wed, Jul 18, 2018 at 03:10:54PM +, Friscia, Michael wrote: > We have a problem where we have a large number of vanity domain > names that are redirected. For example we have surgery.yale.edu > which redirects to medicine.yale.edu/surgery. This works fine > until someone tries to

Re: Redirect without and SSL certificate

2018-07-18 Thread Jeff Abrahamson
Could you use letsencrypt to manage all those certs? What you want can't work: the client makes an SSL request, you respond (with a 301), the client detects that the interaction was not properly authenticated, and so complains to the user.  It's out of your hands, which is the whole point of SSL

Re: limit_req applied to upstream auth_request requests?

2018-07-18 Thread jarstewa
Maxim Dounin Wrote: --- > The explanation on why it isn't working was in the first paragraph > I wrote: > > : The limit_req directive doesn't try to limit requests already > : limited, as well as subrequests within these requests. You should

Re: limit_req applied to upstream auth_request requests?

2018-07-18 Thread Maxim Dounin
Hello! On Tue, Jul 17, 2018 at 05:23:44PM -0400, jarstewa wrote: [...] > So, I think you seem to be suggesting that throttling /auth should not be > necessary, and may in fact be a bad idea. But I would still like to > understand why it isn't working as I would expect. The explanation on why

[nginx] Fixed invalid access to location defined as an empty string.

2018-07-18 Thread Ruslan Ermilov
details: http://hg.nginx.org/nginx/rev/45e513c3540d branches: changeset: 7321:45e513c3540d user: Ruslan Ermilov date: Tue Jul 17 15:30:43 2018 +0300 description: Fixed invalid access to location defined as an empty string. diffstat: src/http/modules/ngx_http_fastcgi_module.c |

[njs] String.bytesFrom() method.

2018-07-18 Thread Dmitry Volyntsev
details: http://hg.nginx.org/njs/rev/9322e8eab0b6 branches: changeset: 560:9322e8eab0b6 user: Dmitry Volyntsev date: Wed Jul 18 15:41:55 2018 +0300 description: String.bytesFrom() method. The method creates a byte string from an array containing octets: String.bytesFrom(array).

Re: ngx ssl certificates вызывается даже для сайтов без ssl

2018-07-18 Thread Alex Vorona
Здравствуйте, 18.07.18 13:10, Vitaly Ponomarev wrote: Добрый день. Насколько допустимо посылать HUP сразу всем процессам nginx при условии, что в данной виртуалке запущен только один демон nginx'а? Т.е. делать вот так: == killall -HUP nginx == pkill -f "nginx: master" -HUP Ну и/или другие

Re: ngx ssl certificates вызывается даже для сайтов без ssl

2018-07-18 Thread Maxim Dounin
Hello! On Wed, Jul 18, 2018 at 01:10:55PM +0300, Vitaly Ponomarev wrote: > Насколько допустимо посылать HUP сразу всем процессам nginx при > условии, что в данной виртуалке запущен только один демон > nginx'а? > Т.е. делать вот так: > == > killall -HUP nginx > == Конкретно HUP - рабочими

Re[2]: ngx ssl certificates вызывается даже для сайтов без ssl

2018-07-18 Thread Vitaly Ponomarev
Добрый день. Насколько допустимо посылать HUP сразу всем процессам nginx при условии, что в данной виртуалке запущен только один демон nginx'а? Т.е. делать вот так: == killall -HUP nginx == >Вторник, 17 июля 2018, 16:07 +03:00 от Maxim Dounin : > >Hello! > >On Tue, Jul 17, 2018 at 02:40:18AM