Hey Mark et. al.,
On Tue, 7 Jan 2020 at 11:20, Mark Thomas wrote:
> On 12/12/2019 15:23, Christopher Schultz wrote:
> > Arief,
> >
> > On 12/12/19 00:25, Arief Hasani wrote:
> >> IMHO, being able to override form HTTP1.1 conf is all good as user
> >> could easily assume that if not specified in
On 12/12/2019 15:23, Christopher Schultz wrote:
> Arief,
>
> On 12/12/19 00:25, Arief Hasani wrote:
>> 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
> I'm not sure you understand the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arief,
On 12/12/19 00:25, Arief Hasani wrote:
> 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
I'm not sure you understand the question.
Hi Mark,
I 've been using tomcat for many years and the cases were I had to modify
the http connector defaults were very rare. I would go for the simplest
solution.
Hope it helps and thank you so mch to you and the rest of the
committers!
Luis
El jue., 12 dic. 2019 a las 6:25,
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:
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/25/17 5:14 PM, Mark Thomas wrote:
> On 25/01/2017 22:11, Zigarelli, Michael wrote:
>> Hi,
>>
>>
>> I am unable to configure tomcat 9.0.0.M17 for http/2 support. My
>> connector for port 8443 has been uncommented and the necessary
>>
On 25/01/2017 22:11, Zigarelli, Michael wrote:
> Hi,
>
>
> I am unable to configure tomcat 9.0.0.M17 for http/2 support. My connector
> for port 8443 has been uncommented and the necessary certificates were added
> to it. I am receiving this error when I start my tomcat: Jan 25, 2017 4:28:21
Hi,
I am unable to configure tomcat 9.0.0.M17 for http/2 support. My connector for
port 8443 has been uncommented and the necessary certificates were added to it.
I am receiving this error when I start my tomcat: Jan 25, 2017 4:28:21 PM
org.apache.catalina.util.LifecycleBase
11 matches
Mail list logo