Re: HTTP/2 configuration

Hi Mark, IMHO, being able to override form HTTP1.1 conf is all good as user could easily assume that if not specified in the upgrade than use http1.1 configs Cheers - To unsubscribe, e-mail:

Re: remote jmx monitoring through ssh tunnel

Chris > Am 11.12.2019 um 21:46 schrieb Chris Cheshire >: > > Peter, > > On Wed, Dec 11, 2019 at 2:38 AM Peter Kreuser > wrote: >> >> Chris‘, >> >>> Am 10.12.2019 um 18:59 schrieb Chris Cheshire >> >: >>>

Re: remote jmx monitoring through ssh tunnel

On Wed, Dec 11, 2019 at 12:24 PM Christopher Schultz wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > > On 12/10/19 12:59, Chris Cheshire wrote: > > On Tue, Dec 10, 2019 at 11:58 AM Chris Cheshire > > wrote: > >> > >> On Tue, Dec 10, 2019 at 9:42 AM Christopher Schultz > >>

Re: remote jmx monitoring through ssh tunnel

Peter, On Wed, Dec 11, 2019 at 2:38 AM Peter Kreuser wrote: > > Chris‘, > > > Am 10.12.2019 um 18:59 schrieb Chris Cheshire : > > > > On Tue, Dec 10, 2019 at 11:58 AM Chris Cheshire > > wrote: > >> > >>> On Tue, Dec 10, 2019 at 9:42 AM Christopher Schultz > >>> wrote: > >>> > >>> -BEGIN

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 12/11/19 13:01, Mark Thomas wrote: > On 11/12/2019 17:43, Christopher Schultz wrote: > > > >>> I'm not sure why we need this over and above the RequestFacade >>> object. >> >> The RequestFacade is intended to protect the container

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

On 11/12/2019 17:43, Christopher Schultz wrote: >> I'm not sure why we need this over and above the RequestFacade >> object. > > The RequestFacade is intended to protect the container from the > application, right? It can cut both ways. > And they are (usually) re-used. If a RequestFacade >

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 12/10/19 10:36, Mark Thomas wrote: > On 10/12/2019 14:27, Christopher Schultz wrote: > > > >> Would using org.apache.catalina.connector.RECYCLE_FACADES=true >> have made this problem go away? Or would the behavior have been >> the same,

Re: Expected behavior of calling javax.servlet.ServletRequest#getInputStream after javax.servlet.http.HttpServletRequest#getPart

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 12/10/19 16:47, André Warnier (tomcat/perl) wrote: > On 10.12.2019 15:31, Christopher Schultz wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> Behrang, >> >> On 12/8/19 05:18, Behrang Saeedzadeh wrote: >>> If I call

Re: remote jmx monitoring through ssh tunnel

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/10/19 12:59, Chris Cheshire wrote: > On Tue, Dec 10, 2019 at 11:58 AM Chris Cheshire > wrote: >> >> On Tue, Dec 10, 2019 at 9:42 AM Christopher Schultz >> wrote: >>> >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >>> >>> Chris,

Re: HTTP/2 configuration

On December 11, 2019 11:54:40 AM UTC, "M. Manna" wrote: >Mark, > >On Wed, 11 Dec 2019 at 11:48, Mark Thomas wrote: > >> All, >> >> The Tomcat committers are looking for some user feedback. >> >> Currently, the HTTP/2 protocol configuration [1] duplicates many >> attributes of the HTTP/1.1

Re: HTTP/2 configuration

Mark, On Wed, 11 Dec 2019 at 11:48, Mark Thomas wrote: > All, > > The Tomcat committers are looking for some user feedback. > > Currently, the HTTP/2 protocol configuration [1] duplicates many > attributes of the HTTP/1.1 protocol [2] it is nested under. > > We are considering simplifying this

HTTP/2 configuration

All, The Tomcat committers are looking for some user feedback. Currently, the HTTP/2 protocol configuration [1] duplicates many attributes of the HTTP/1.1 protocol [2] it is nested under. We are considering simplifying this for Tomcat 10 onwards and having the HTTP/2 protocol simply inherit the

Re: Expected behavior of calling javax.servlet.ServletRequest#getInputStream after javax.servlet.http.HttpServletRequest#getPart

ср, 11 дек. 2019 г. в 13:06, Behrang Saeedzadeh : > > Thanks Andre for explaining it much better than I did. > > I posted this to Jakarta EE's mailing list too: > https://www.eclipse.org/lists/jakarta.ee-community/msg01477.html > > I think at least the JavaDocs comments and the spec need minor

Re: Expected behavior of calling javax.servlet.ServletRequest#getInputStream after javax.servlet.http.HttpServletRequest#getPart

Thanks Andre for explaining it much better than I did. I posted this to Jakarta EE's mailing list too: https://www.eclipse.org/lists/jakarta.ee-community/msg01477.html I think at least the JavaDocs comments and the spec need minor amendments to document this expected behaviour clearly. Best