Re[2]: HTTP/2 streams reset by Tomcat are treted as 503 errors by Apache HTTP Server

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

Re[2]: HTTP/2 streams reset by Tomcat are treted as 503 errors by Apache HTTP Server

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

Re[2]: HTTP/2 streams reset by Tomcat are treted as 503 errors by Apache HTTP Server

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

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 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