You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2024/02/06 07:29:42 UTC

[Bug 68533] Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR

https://bz.apache.org/bugzilla/show_bug.cgi?id=68533

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #3 from Mark Thomas <ma...@apache.org> ---
This is an application bug, not a Tomcat bug.

Reviewing the logs shows the following:
- the problems start in stream 55
- the request is processed correctly
- a 304 response is sent

So far, so good. Note that as per the HTTP specs (see RFC 9110, section 15.4.5)
304 responses cannot contain a response body.

At this point the application attempts to send a response body. That triggers
error handling that results in the closure of the HTTP/2 connection. Arguably,
Tomcat could handle this differently and ignore the attempt to write the body
or throw an IllegalStateException or similar but that is only working around
the application misbehaviour.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org