|
From: | Dan Frumin |
Subject: | bug#36350: [2.2.5] ‘read-headers’ blocks, thereby breaking web servers |
Date: | Mon, 24 Jun 2019 14:44:58 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 |
By the way, I've just tested the web server in Google Chrome, and it works fine!I was told that a (potential) reason for that is that Chrome sends TCP FIN to the server, which closes the socket for reading, and then `lookahead-char` sees eof.
Best, Dan
[Prev in Thread] | Current Thread | [Next in Thread] |