How to handle Expect: 100-continue

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 -- View this message in context: http://www.nabble.com/How-to-handle-Expect%3A-100

Re: How to handle Expect: 100-continue

...@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

Re: How to handle Expect: 100-continue

That is how it is with every single request. Tomcat will never read a body unless the servlet initiates the action. So to read a body you can either - read the input stream - read the reader - issue a request.getParameter (if the body is form encoded, tomcat will read the body and parse the

Re: How to handle Expect: 100-continue

? -- View this message in context: http://www.nabble.com/How-to-handle-Expect%3A-100-continue-tp21440164p21445613.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr

Re: How to handle Expect: 100-continue

Nathan Ashworth wrote: Thanks, Filip. Upon further investigation, we've discovered that our POSTs were bigger than the default maxPostSize value (2MB). The call to getParameter(foo) was returning null and doing a trace showed that the client was not sending the body. good catch It appears