I hope this is the appropriate place to report this. I struggled with using
the alias directive because I (incorrectly) assumed that it was relative to
root since all other parts of my nginx configs are. This is not mentioned in
the documentation, it'd be nice to see it there.
If I'm completely of
Nginx does not validate the expiration date of certificates.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,286852,286857#msg-286857
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wed, Jan 29, 2020 at 08:39:16AM -0500, MarcoI wrote:
Hi there,
> So may be my nginx configuration has to be improved.
What request do you make?
What response do you get?
What response do you want to get, instead?
If you can use something like "curl -v" to show one specific request
that get
On Wed, Jan 29, 2020 at 07:12:24PM +, Johan Gabriel Medina Capois wrote:
Hi there,
> The issues is that nginx is not allowing authentication through, any
> application cant’s authenticate through nginx, is this case the backend is
> running in IIS, any idea? if you need more information i
The issues is that nginx is not allowing authentication through, any
application cant’s authenticate through nginx, is this case the backend is
running in IIS, any idea? if you need more information i can send what ever
you need, but please a need your help.
Regards
From: nginx On Behalf Of
Does nginx validates all the Cerificates in the certificate chain?
Like the expiry date of the all the intermediate certificates.
If one the intermediate certificate has expired will nginx still proceed or
will it break the connection?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,2
Add-on to the previous email:
using firefox as web browser, I get this error message:
https://drive.google.com/open?id=1l6USIHrbHl6kBcQtormXplOgx0J653ko
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at https://localhost/sockjs-node/info?t=1580304400
I created a brand new tiny webapp with vue cli, so without adding anything,
apart from what the empty vue-cli scaffolding brings:
(base) marco@pc:~/vueMatters/testproject$ npm run serve
> testproject@0.1.0 serve /home/marco/vueMatters/testproject
> vue-cli-service serve
INFO Sta
