Re: Tomcat Large Payload Truncated

2020-06-29 Thread Bhavesh Mistry
Hi Mark, Thank you for responding. I have one more question. This is spring-boot 2 application REST API server and it does not accept Cookie or session (timeout is set to zero).Auth happens through Authorized header. We have set 10mb for maxPostSize. Does maxSavePostSize takes precedence

Tomcat Large Payload Truncated

2020-06-28 Thread Bhavesh Mistry
Hi All, I am running embedded *tomcat*-embed-core-9.0.36.jar and large payload *179292* and HTTPS 1.1 traffic. When I use curl command with transfer encoding or without, both request JSON payload is truncated, and the application can not parse it. The smaller payload works fine. Both small

Tomcat 9.0.31 Invalid character found in the request target

2020-03-04 Thread Bhavesh Mistry
Hi Tomcat Team, When there is invalid characters, it return error message with stacktrace as shown below. 1) is there any way to costmize error message ? if yes, please let me know. 2) Is there any way to spress stack-trace being shown on 400 bad request ? 3) Based on Accept header

Re: Tomcat 9.31 PUT/POST Request receiving Partial Data

2020-02-26 Thread Bhavesh Mistry
The response get truncated after 16321 bytes. Please let me know what is best way to wait and in order to consume entire request payload. Thanks, Bhavesh On Wed, Feb 26, 2020 at 4:34 PM Bhavesh Mistry wrote: > Hi Tomcat Team, > > I have servlet filter for all requests to cache the e

Tomcat 9.31 PUT/POST Request receiving Partial Data

2020-02-26 Thread Bhavesh Mistry
Hi Tomcat Team, I have servlet filter for all requests to cache the entire PUT/POST Payload. When content is large 4KB or more, I am getting partial content when I read from HttpServletRequest.getInputStream(). But I but 10 seconds wait before consuming the input stream, I am getting entire

Re: Fwd: Tomcat-embed-core-9.0.12.jar bug about Content-Length Corrupting Parsing logic for Subsequent Request

2019-02-07 Thread Bhavesh Mistry
< chuck.caldar...@unisys.com> wrote: > > From: Bhavesh Mistry [mailto:mistry.p.bhav...@gmail.com] > > Subject: Re: Fwd: Tomcat-embed-core-9.0.12.jar bug about Content-Length > Corrupting > > Parsing logic for Subsequent Request > > > I am stating following when you h

Re: Fwd: Tomcat-embed-core-9.0.12.jar bug about Content-Length Corrupting Parsing logic for Subsequent Request

2019-02-07 Thread Bhavesh Mistry
look request/response model, how can tomcat read ahead on PUT call on a socket the data is not there? Thanks, Bhavesh On Thu, Feb 7, 2019 at 1:51 PM Mark Thomas wrote: > On 07/02/2019 20:05, Bhavesh Mistry wrote: > > Hi Mark, > > > > There is no way to validate the END

Re: Fwd: Tomcat-embed-core-9.0.12.jar bug about Content-Length Corrupting Parsing logic for Subsequent Request

2019-02-07 Thread Bhavesh Mistry
tty ---> Apache-Camel HTTP Proxy ---> tomcat (Spring boot). The failure on the SAME TCP occurs at tomcat, not at Jetty for the same TCP connection. Thanks, Bhavesh On Thu, Feb 7, 2019 at 11:25 AM Mark Thomas wrote: > On 07/02/2019 18:48, Bhavesh Mistry wrote: > > Hello Tomcat Develope

Fwd: Tomcat-embed-core-9.0.12.jar bug about Content-Length Corrupting Parsing logic for Subsequent Request

2019-02-07 Thread Bhavesh Mistry
Hello Tomcat Developers, I have a unique situation about HTTP Protocol PAYLOAD parsing and Content-Length Header. When PUT/POST Content-Length is NOT correct (client send wrong Content-Lenght), the tomcat is able to parse the request and respond to request with 2xx but subsequent on SAME TCP