Hi,
When a client disconnects (initiated tcp FIN), shouldn't we see 499 in
nginx logs? But sometimes I see 400, along with below in error log:
*2314539 client prematurely closed connection, client: x.x.x.x,
Since I don't see "while reading client request headers" in the error log,
I assume the re
> On 24 Nov 2020, at 21:17, j...@fuldgroup.com wrote:
>
> Hi All,
>
> Found an issue within the build of nginx.
>
> Following James’ instructions on
> https://www.nginx.com/blog/video-streaming-for-remote-learning-with-nginx/ :
> mkdir buildnginx
> cd buildnginx
> sudo git clone https://gith
Hi All,
Found an issue within the build of nginx.
Following James' instructions on
https://www.nginx.com/blog/video-streaming-for-remote-learning-with-nginx/ :
mkdir buildnginx
cd buildnginx
sudo git clone https://github.com/arut/nginx
Hi,
I have two nginx.conf file /etc/nginx/conf.d/onetest.conf
and /etc/nginx/nginx.conf. Basically the first config file works without
any issue while redirecting from port 80 to 443. I want to enable the port
redirect from port 80 to 443 in /etc/nginx/nginx.conf. when I add the below
block in /et
Hello,
I run a nginx instance handling only TLS1.2 and TLS1.3.
Now I noticed an remote client hammering (Ok, once per second) with an SSLv2
connection an thus filling the log:
2020/11/24 17:37:08 [info] 383#0: *11 SSL_do_handshake() failed (SSL:
error:14209102:SSL routines:tls_early_post_proces
Hello!
On Thu, Nov 19, 2020 at 02:06:46PM -0800, Frank Liu wrote:
> CVE-2019-20372 mentioned a security vulnerability, but I don't see it in
> http://nginx.org/en/security_advisories.html
> Does that mean CVE-2019-20372 is not considered a security vulnerability by
> nginx? Or is it because nginx
Changes with nginx 1.19.524 Nov 2020
*) Feature: the -e switch.
*) Feature: the same source files can now be specified in different
modules while building addon modules.
*) Bugfix: SSL shutdown did not work when lingering close was used.