On 06/11/2018 00:02, Amit Pande wrote:
> Thanks Mark for the update. Seems like there is a potential bug in our client
> components which happened to keep on adding to existing header list.
>
> https://tomcat.apache.org/tomcat-8.5-doc/config/http.html
>
> From the documentation:
>
> maxHttpHea
Thanks Mark for the update. Seems like there is a potential bug in our client
components which happened to keep on adding to existing header list.
https://tomcat.apache.org/tomcat-8.5-doc/config/http.html
From the documentation:
maxHttpHeaderSize :The maximum size of the request and response H
On 03/11/2018 01:35, Amit Pande wrote:
> Thanks Chris. Yes, I will soon send out the patch for review.
Logically, I can see some hurdles for such a patch that are going to be
difficult to overcome.
Tomcat will process all of the received data up to the limit. It is on
the subsequent read to get m
Thanks Chris. Yes, I will soon send out the patch for review.
Thanks,
Amit
On 11/2/18, 5:25 PM, "Christopher Schultz"
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amit,
On 11/2/18 17:16, Amit Pande wrote:
> As per current implementation (below snippet i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amit,
On 11/2/18 17:16, Amit Pande wrote:
> As per current implementation (below snippet is from 8.5.28), if
> the request header is too large (by default >8K, the default
> maxHttpHeaderSize), is thrown below error message is seen.
>
>
> For req
As per current implementation (below snippet is from 8.5.28), if the request
header is too large (by default >8K, the default maxHttpHeaderSize), is thrown
below error message is seen.
For request --
02-Nov-2018 15:15:47.649 INFO [catalina-exec-40]
org.apache.coyote.http11.Http11Processor.serv
