New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net/http: malformed HTTP request when GET follows HEAD request #5522
Labels
Comments
Labels changed: added priority-soon, go1.1.1, removed priority-triage. Owner changed to @bradfitz. |
I don't believe either of those servers are speaking valid HTTP. javascript.ru is sending a body in response to a HEAD request and example.iana.org is replying with HTTP/1.1 200 OK and closing the connection immediately without sending a "Connection: close" header (keep-alive is the default in HTTP/1.1 if not said otherwise). HEAD / HTTP/1.1 Host: javascript.ru Accept-Encoding: gzip HTTP/1.1 200 OK Server: nginx/1.2.1 Date: Tue, 21 May 2013 20:50:44 GMT Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: vblastvisit=1369169444; expires=Wed, 21-May-2014 20:50:44 GMT; path=/; domain=.javascript.ru Set-Cookie: vblastactivity=0; expires=Wed, 21-May-2014 20:50:44 GMT; path=/; domain=.javascript.ru Cache-Control: store, no-cache, must-revalidate Pragma: private Expires: Sun, 19 Nov 1978 05:00:00 GMT Last-Modified: Tue, 21 May 2013 20:50:44 GMT Cache-Control: post-check=0, pre-check=0 Content-Encoding: gzip ���(binary gibberish) It looks like an nginx bug. It at least does appear that nginx does the right thing if we don't send it a "Accept-Encoding: gzip" header. I can fix that at least. |
This issue was closed by revision ddda798. Status changed to Fixed. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: