It could be because TC reads and parses the the input stream for you, so you can get them though request.getParameter (and other methods).
If the request content type is something different (e.g. xml/text ), you would have the input stream then and read it the way you want. This is just my guess, sorry if this didn't turn to be right. On Mon, Aug 18, 2008 at 8:07 PM, deniak <[EMAIL PROTECTED]> wrote: > > Hi all, > > Has anyone ever used a form with "x-www-form-urlencoded" Content-Type to a > web application running on tomcat? > I don't know why but when I use that kind of Content-Type, my inputstream > is > empty. > There's no problem if I use another Content-Type. > It seems there's a problem with coyote connector but I can't figure out > what > it is... > > Any clue? > -- > View this message in context: > http://www.nabble.com/Post-form-with-%22x-www-form-urlencoded%22-content-type-and-Coyote-Connector-tp19035430p19035430.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Youssef
