Re: HTTP response reason phrases

2017-01-29 Thread Josh Soref
Rainer Jung wrote: > the old spec states "The Reason-Phrase is intended to give a short textual > description of the Status-Code. > The ... Reason-Phrase is intended for the human user." "human user" should be a pretty big clue that a UA should not be using it to make any decisions. Any UA that

Re: HTTP response reason phrases

2017-01-25 Thread Huxing Zhang
Hi, I think the problem is that how we target tomcat 8.5 to the users. Is it a biased to 8.0, or is it biased to 9.0? For the former case, we should keep the backward compatibility as much as possible. For the latter case, breaking things should be assumable by end users. IMO, 8.5 should be the

Re: HTTP response reason phrases

2017-01-25 Thread Rémy Maucherat
2017-01-24 20:08 GMT+01:00 Christopher Schultz : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > All, > > I'm cross-posting dev@ and users@, but please only reply to dev@ if > you'd like to get involved in this discussion. > > I'd like to openly-discuss

Re: HTTP response reason phrases

2017-01-25 Thread Romain Manni-Bucau
2017-01-25 20:51 GMT+01:00 Christopher Schultz : > Romain, > > On 1/25/17 5:30 AM, Romain Manni-Bucau wrote: > > 8.5 just being almost a N-1 spec version of tomcat 9 I think they should > > stay aligned as much as possible. > > Yes, but 8.5 is a N+0 spec version of

Re: HTTP response reason phrases

2017-01-25 Thread Christopher Schultz
Romain, On 1/25/17 5:30 AM, Romain Manni-Bucau wrote: > 8.5 just being almost a N-1 spec version of tomcat 9 I think they should > stay aligned as much as possible. Yes, but 8.5 is a N+0 spec version of Tomcat 8.0. I think since Tomcat 8.5 is being pushed as the hurry-up upgrade for Tomcat 8.0,

Re: HTTP response reason phrases

2017-01-25 Thread Romain Manni-Bucau
Hi guys, 8.5 just being almost a N-1 spec version of tomcat 9 I think they should stay aligned as much as possible. Also note that fixing it in 8.5 will just delay the issue for 9.x. I'm not sure I see the blocking point to add a configuration for that (agree it is not spec compliant but it is a

Re: HTTP response reason phrases

2017-01-25 Thread Rainer Jung
Am 25.01.2017 um 11:09 schrieb Rainer Jung: Am 24.01.2017 um 21:03 schrieb Mark Thomas: On 24/01/2017 19:08, Christopher Schultz wrote: I'm wondering what the wider community thinks about this change and whether or not we should consider reverting it for Tomcat 8.5.x. 8.5.x has been out for

Re: HTTP response reason phrases

2017-01-25 Thread Rainer Jung
Am 24.01.2017 um 21:03 schrieb Mark Thomas: On 24/01/2017 19:08, Christopher Schultz wrote: I'm wondering what the wider community thinks about this change and whether or not we should consider reverting it for Tomcat 8.5.x. 8.5.x has been out for 10 months and stable for 7. It is probably

Re: HTTP response reason phrases

2017-01-24 Thread Josh Soref
Christopher Schultz wrote: > I'm wondering what the wider community thinks about this change and > whether or not we should consider reverting it for Tomcat 8.5.x. Mark Thomas wrote: > The root cause is non-specification compliant clients. I generally don't > view specification non-compliance in

Re: HTTP response reason phrases

2017-01-24 Thread Mark Thomas
On 24/01/2017 19:08, Christopher Schultz wrote: > I'm wondering what the wider community thinks about this change and > whether or not we should consider reverting it for Tomcat 8.5.x. 8.5.x has been out for 10 months and stable for 7. It is probably still early enough that we are seeing issues

HTTP response reason phrases

2017-01-24 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm cross-posting dev@ and users@, but please only reply to dev@ if you'd like to get involved in this discussion. I'd like to openly-discuss r1702765 [1]. There have been some complaints on both users@ and dev@ and some BZ issues filed