On 07/02/2019 18:48, Bhavesh Mistry wrote: > Hello Tomcat Developers, > > I have a unique situation about HTTP Protocol PAYLOAD parsing and > Content-Length Header.
There is nothing unique here. > 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 > connection fails with corrupted HTTP HEADER. As expected. Tomcat can't read minds. If the content length header is not correct, Tomcat can't correctly identify the end of the request so it is going to read too much / too little and - on a keep-alive connection - the next request is going to fail. There is nothing unusual about this. There is no Tomcat bug here. You need to fix the broken client so the content-length is correctly set. You could disable keep-alive connections. That would limit the failures to the faulty requests but at the cost of reduced performance. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
