omas ma...@apache.org wrote:
>>
>>> On 27/10/18 14:38, Caldarale, Charles R wrote:
>>>
>>>>> From: Mani
>>>>> [mailto:mani.chandraseka...@protonmail.com.INVALID]
>>>>> Subject: Handling empty Host in HTTP Header
>>>&g
t;
> > > > From: Mani [mailto:mani.chandraseka...@protonmail.com.INVALID]
> > > > Subject: Handling empty Host in HTTP Header
> > >
> > > > May I know, when is the next official tomcat release planned?
> > >
> > > Releases for Tomcat versions under activ
‐‐‐ Original Message ‐‐‐
On Saturday, October 27, 2018 8:52 PM, Mark Thomas wrote:
> On 27/10/18 14:38, Caldarale, Charles R wrote:
>
> > > From: Mani [mailto:mani.chandraseka...@protonmail.com.INVALID]
> > > Subject: Handling empty Host in HTTP Header
&g
On 27/10/18 14:38, Caldarale, Charles R wrote:
>> From: Mani [mailto:mani.chandraseka...@protonmail.com.INVALID]
>> Subject: Handling empty Host in HTTP Header
>
>> May I know, when is the next official tomcat release planned?
>
> Releases for Tomcat versio
‐‐‐ Original Message ‐‐‐
On Saturday, October 27, 2018 7:08 PM, Caldarale, Charles R
wrote:
> > From: Mani [mailto:mani.chandraseka...@protonmail.com.INVALID]
> > Subject: Handling empty Host in HTTP Header
>
> > May I know, when is the next official t
> From: Mani [mailto:mani.chandraseka...@protonmail.com.INVALID]
> Subject: Handling empty Host in HTTP Header
> May I know, when is the next official tomcat release planned?
Releases for Tomcat versions under active development (including the 8.5
leg) normally occur in the first wee
Hi,
We are using tomcat-8.5.34. One of our client code is sending a POST
request with HTTP header parameter "Host", as an empty string. And 8.5.34
version of tomcat is rejecting the connection with a 400 Error. After
debugging, we found that the parseHost API in
