Sorry I guess I meant 401 instead of 5xx? Well, same question tho.
by the way, i changed to
nginx basic_auth and when I enter
wrong
credentials, it allows me endless tries. i'm was
used
to apache gives a 5xx page after three
bad tries. i gues
by the way, i changed to nginx basic_auth and when I enter
wrong credentials, it allows me endless tries. i'm was used
to apache gives a 5xx page after three bad tries. i guess you
could refresh that and try again in apache too, but endless
tries without a error for nginx? is there a way to chan
Hello,
I have set up HTTP auth using the auth_pam module (although
I'm not sure that module is the problem - it might be nginx problem).
https://github.com/stogh/ngx_http_auth_pam_module/
All works great for a while
After some time, browsers begin to prompt for authentication over
and over
My web server is intentionally set up to only support virtual hosts and TLS
SNI. I know that the latter eliminates some ancient web browsers but I
don't care about those browsers.
I want to enable OCSP stapling and it seems to be configured correctly in my
test vhost (everything else about SSL al
If nginx manages those files like the others (like logs), it (re)opens them
on reload/restart.
You might tweak your updating script to also send a HUP signal to nginx. It
would be recommanded to check the error log on reload, as errors (if any)
will appear there.
You might also simply use the ssl_
Hey all.
Before I file a bugreport I'd like to consult with community to make sure
whether I get the whole thing right.
I use ssl_stapling_file and update that file daily.
Today I discovered that one of my SSL websites returns outdated OCSP
response, not the one which is in the OCSP stapling file:
