Chrome Version       : 53.0.2785.89 (Official Build) m (32-bit)
URLs (if applicable) : -
Other browsers tested:
     Safari: -
    Firefox: OK
         IE: -

What steps will reproduce the problem?
(1) Send a big POST request.
(2) Server answers request before the complete request has been sent.


What is the expected result?
Browser stops sending further DATA frames, because the stream has already been closed by the server by sending a response.


What happens instead?
The complete request body is sent although the server's last DATA frame (containing the response body) has the flag END_STREAM. As consequence the stream is in state “closed”. 

RFC7540 (chapter 5.1): 
"An endpoint MUST NOT send frames other than PRIORITY on a closed stream."


I attached the output of net-internal. It shows that a big POST request is sent on stream 55. A "400 Bad Request" response is sent by the server but the client continues to send further DATA frames.
 

Deleted: net-internals.html 1.9 MB

net-internals.html 1.9 MB View Download