Re: logrotate (?) screws it badly
* lejeczek via nginx: > For after logs got rotated Nginx logs into: > access.log.1 & error.log.1 > and now as it should, you know > access.log & error.log You may want to try logrotate's "copytruncate" option. -Ralph ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
Re: Can I rewrite https to http?
* baalch...@gmail.com: > So, can I redirect the request, when user open https://nossl.abc.com, the > will be redirect to http://nossl.abc.com? While technically possible, you might find that connecting clients may interpret this as a "downgrade attack", because the client asked for an encrypted connection. Obtaining a certificate from Let's Encryt or similar seems a more suitable approach to me. -Ralph ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
