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 questi
-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.
Mar
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, Ari
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: users-unsubscr...@tomcat.apache.or
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 protoco
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 f
