net::ERR_HTTP2_PROTOCOL_ERROR errors in version 10.1.29

2024-09-13 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello,
after upgrading from 10.1.25 to 10.1.29 I experience many 
net::ERR_HTTP2_PROTOCOL_ERROR in Edge and Chrome.
Firefox shows NS_ERROR_NET_RESET.
The website doesn't fully render.

Access-Log shows several HTTP 500 errors for static resources.
The other logfiles don't show any errors.

Does anybody observer the same issues?

My connector looks like:









Thanks in advance!
Thomas


Re: net::ERR_HTTP2_PROTOCOL_ERROR errors in version 10.1.29

2024-09-13 Thread Rémy Maucherat
On Fri, Sep 13, 2024 at 11:58 AM Thomas Hoffmann (Speed4Trade GmbH)
 wrote:
>
> Hello,
> after upgrading from 10.1.25 to 10.1.29 I experience many 
> net::ERR_HTTP2_PROTOCOL_ERROR in Edge and Chrome.
> Firefox shows NS_ERROR_NET_RESET.
> The website doesn't fully render.
>
> Access-Log shows several HTTP 500 errors for static resources.
> The other logfiles don't show any errors.
>
> Does anybody observer the same issues?

You can use 10.1.28 instead for now, the regression is being worked on.

Rémy

> My connector looks like:
>
>  protocol="org.apache.coyote.http11.Http11NioProtocol"
>
> sslImplementationName="org.apache.tomcat.util.net.openssl.OpenSSLImplementation"
>maxThreads="150" minSpareThreads="25"
>URIEncoding="UTF-8" useBodyEncodingForURI="false"
>enableLookups="false" disableUploadTimeout="true"
>acceptCount="100" scheme="https" secure="true"
>SSLEnabled="true"
>compression="force">
>  className="org.apache.coyote.http2.Http2Protocol"  />
>  ciphers="ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384"
> disableSessionTickets="true"
> honorCipherOrder="false"
> protocols="+TLSv1.2,+TLSv1.3">
>  certificateFile="localhost.pem"   type="RSA"/>
> 
> 
>
>
> Thanks in advance!
> Thomas

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



AW: net::ERR_HTTP2_PROTOCOL_ERROR errors in version 10.1.29

2024-09-13 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello,
thank you for the quick reply!
I will wait for the next release / fix.

> -Ursprüngliche Nachricht-
> Von: Rémy Maucherat 
> Gesendet: Freitag, 13. September 2024 12:48
> An: Tomcat Users List 
> Betreff: Re: net::ERR_HTTP2_PROTOCOL_ERROR errors in version 10.1.29
> 
> On Fri, Sep 13, 2024 at 11:58 AM Thomas Hoffmann (Speed4Trade GmbH)
>  wrote:
> >
> > Hello,
> > after upgrading from 10.1.25 to 10.1.29 I experience many
> net::ERR_HTTP2_PROTOCOL_ERROR in Edge and Chrome.
> > Firefox shows NS_ERROR_NET_RESET.
> > The website doesn't fully render.
> >
> > Access-Log shows several HTTP 500 errors for static resources.
> > The other logfiles don't show any errors.
> >
> > Does anybody observer the same issues?
> 
> You can use 10.1.28 instead for now, the regression is being worked on.
> 
> Rémy
> 
> > My connector looks like:
> >
> >  protocol="org.apache.coyote.http11.Http11NioProtocol"
> >
> sslImplementationName="org.apache.tomcat.util.net.openssl.OpenSSLImple
> mentation"
> >maxThreads="150" minSpareThreads="25"
> >URIEncoding="UTF-8" useBodyEncodingForURI="false"
> >enableLookups="false" disableUploadTimeout="true"
> >acceptCount="100" scheme="https" secure="true"
> >SSLEnabled="true"
> >compression="force">
> >  className="org.apache.coyote.http2.Http2Protocol"  />
> >  > disableSessionTickets="true"
> > honorCipherOrder="false"
> > protocols="+TLSv1.2,+TLSv1.3">
> >  certificateFile="localhost.pem"   type="RSA"/>
> > 
> > 
> >
> >
> > Thanks in advance!
> > Thomas
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org



[ANN] Apache Tomcat: HTTP/2 regression in 11.0.0-M25, 10.1.29, 9.0.94

2024-09-13 Thread Mark Thomas
A regression has been reported and confirmed in the latest Tomcat 
releases that affects configurations using HTTP/2.


The affected versions are:
- 11.0.0-M25
- 10.1.29
- 9.0.94

The regression can be worked around by setting:

discardRequestsAndResponses="true"

on the UpgradeProtocol element for HTTP/2.

We currently expect to provide releases with a fix for this regression 
next week.


For more information, see the associated bug report:
https://bz.apache.org/bugzilla/show_bug.cgi?id=69320

- The Apache Tomcat team

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org