The problem is that with some MIDP implementations, even if you set the content-length, the implementation, or possibly some gateway, can change the request to chunked. I believe they would do this in order to control the flow of data the mobile network. In our case this does, in fact, happen. We can in this particular application, parse it ourselves, but this is not always an option as you could be POSTing to some arbitrary URL. So, what to do?
Adrian > -----Original Message----- > From: Remy Maucherat [mailto:remm@;apache.org] > Sent: Friday, November 08, 2002 12:10 PM > To: Tomcat Developers List > Subject: Re: Bug(?) and suggested solution for chunked > transfer-encoding > POST request > > > Adrian Sampaleanu wrote: > > > We are having a problem with Catalina 4.1.12 (I believe we also had > > issues with previous versions, but can't say for sure) with > respect to > > how POSTed requests are handled if the transfer encoding is > "chunked". > > It seems that request parameters in the content are not > processed in > > this case. > > This is not legal. In HTTP/1.1, FORM encoded data of a POST > must have a > content-length. You can do the parsing yourself, of course. > > Rémy > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:tomcat-dev-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
