The specification language isn't is tight as I'd like it to be but I think
you're right - the intention of the spec authors was that NO_ERROR gets used
here. I'll get that updated for the next round of releases.
Cool! Thanks a lot, Mark!
--
Lorenzo
On 15/12/2022 22:42, Lorenzo Dalla Vecchia wrote:
I looked at the sources for the HTTP/2 connector and found this code
around line 100 of org.apache.coyote.http2.StreamProcessor.
StreamException se = new StreamException(
sm.getString("streamProcessor.cancel", stream.getConnectionId
On 15/12/2022 22:42, Lorenzo Dalla Vecchia wrote:
Hello.
We are having a random issue in a setup with Tomcat deployed behind Apache
httpd. Some HTTP/2 requests proxied to Tomcat by httpd end with a 503 (service
unavailable) response to the web browser client.
Tomcat version is 9.0.58 running
On 15/12/2022 22:42, Lorenzo Dalla Vecchia wrote:
Hello.
We are having a random issue in a setup with Tomcat deployed behind
Apache httpd. Some HTTP/2 requests proxied to Tomcat by httpd end with a
503 (service unavailable) response to the web browser client.
Tomcat version is 9.0.58 running
Hello Lorenzo,
-Ursprüngliche Nachricht-
Von: Lorenzo Dalla Vecchia
Gesendet: Donnerstag, 15. Dezember 2022 23:42
An: users@tomcat.apache.org
Betreff: HTTP/2 streams reset by Tomcat are treted as 503 errors by Apache
HTTP Server
Hello.
We are having a random issue in a setup
Hello Lorenzo,
> -Ursprüngliche Nachricht-
> Von: Lorenzo Dalla Vecchia
> Gesendet: Donnerstag, 15. Dezember 2022 23:42
> An: users@tomcat.apache.org
> Betreff: HTTP/2 streams reset by Tomcat are treted as 503 errors by Apache
> HTTP Server
>
> Hello.
>
>
Hello.
We are having a random issue in a setup with Tomcat deployed behind
Apache httpd. Some HTTP/2 requests proxied to Tomcat by httpd end with a
503 (service unavailable) response to the web browser client.
Tomcat version is 9.0.58 running with Java 1.8.0 in a Docker container.
Docker vers
