What we are observing is: 1) Client initiates the POST with the 'Expect: 100-continue' header, 2) Tomcat responds with '100 Continue', 3) Tomcat calls the servlet. Now once we are in our servlet, unless we explicitly read from the request's BufferedReader, the client will not send the remainder of the POST.
So, from my perspective, it looks like Tomcat is only handling half of the POST, while it is up to to servlet to read and parse the other half. Is that the expected process when dealing with 100-continue? Filip Hanik - Dev Lists wrote: > > if you use wireshark, you should see that Tomcat already does it > automatically. > if you look at the code StandardWrapperValve.java, it should call > response.acknowledge(), and if the client sent an expect header, tomcat > will write out the 100 continue > Filip > > Nathan Ashworth wrote: >> What's the simplest way to support Expect: 100-continue requests in a >> servlet >> running on Tomcat 6? >> >> My current solution is to look for the "expect" header, check whether its >> value is "100-continue" and if it is, then I get a BufferedReader from >> the >> request [request.getReader()] and dump the contents into a String. I then >> parse that String into a parameter Map. >> >> Now, this does work, but it feels like I am doing work that Tomcat should >> be >> handling transparently. Am I missing something here? >> >> Thanks, >> >> Nathan >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/How-to-handle-Expect%3A-100-continue-tp21440164p21443700.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
