UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0

Example URL:

Steps to reproduce the problem:
1. Install nginx 1.9.14 and configure simple HTTP/2 server:

events {}

http {
    ssl_certificate cert.pem;
    ssl_certificate_key key.pem;

    server {
        listen 4433 ssl http2;
        location / { }
    }
}

2. Make a POST request with non-empty body to any static file (index.html for example);
3. Instead of "405 Not Allowed" error page you will see a blank one.

What is the expected behavior?
RFC 7540 states that "A server can send a complete response prior to the client sending an entire request if the response does not depend on any portion of the request that has not been sent and received. When this is true, a server MAY request that the client abort transmission of a request without error by sending a RST_STREAM with an error code of NO_ERROR after sending a complete response (i.e., a frame with the END_STREAM flag)."

What went wrong?
According to Chromium "net-internals" the RST_STREAM frame with the NO_ERROR code is interpreted as INTERNAL_ERROR, which is very wrong. That prevents Chromium from showing any response from nginx that has been returned without reading the full request body.

Did this work before? No 

Chrome version: 50.0.2661.66 (Developer Build) (64-bit)  Channel: n/a
OS Version: 
Flash Version: Shockwave Flash 11.2 r202

Firefox handles it without any problems.

Initially reported to nginx-devel@ mailing list:
http://mailman.nginx.org/pipermail/nginx-devel/2016-April/008143.html
 

Deleted: trace.txt 52.5 KB

trace.txt 52.5 KB View Download