I just wrote a testcase that uses plain httpclient/jetty, and it doesn't exhibit the problem. (Though is a lot simpler than my application). Could it be related to SSL (which my application uses)?
Anyway, I built the test webapp, and installed it into Jetty at /httpclienttest, and got 15 failures (from 253). All but six of them are cookie-related. Is this any help? Cheers, Simon ----- Original Message ----- From: "Oleg Kalnichevski" <[EMAIL PROTECTED]> To: "Commons HttpClient Project" <[EMAIL PROTECTED]> Cc: "Ingo Brunberg" <[EMAIL PROTECTED]>; "Aurelien Pernoud" <[EMAIL PROTECTED]>; "Simon Roberts" <[EMAIL PROTECTED]> Sent: Wednesday, February 26, 2003 10:25 PM Subject: Re: HTTP Post and HTTP/100 (continue) > Simon, Aurelien, Ingo > > Please help me help you. > > I seem unable to reproduce the problem in my development environment > Redhat 8.0 + Sun JDK 1.2.2 + Tomcat 4.1.18 (running on Sun JDK 1.4.1). > The problem does appear system specific. We need to narrow the problem > down somewhat. The problem appears to manifest itself primarily on > Windows platforms, but it's just a hypothesis at the moment > > Could anyone of you try to come up with a test case that reliably > reproduces the problem? Could you also set up HttpClient test webapp, > run test cases in your environment and let me know the results? > > http://jakarta.apache.org/commons/httpclient/testwebapp.html > > Cheers > > Oleg > > > On Wed, 2003-02-26 at 02:19, Simon Roberts wrote: > > Windows XP, Sun JDK 1.4.1_01 > > > > ----- Original Message ----- > > From: "Oleg Kalnichevski" <[EMAIL PROTECTED]> > > To: "Commons HttpClient Project" <[EMAIL PROTECTED]> > > Sent: Wednesday, February 26, 2003 11:31 AM > > Subject: Re: HTTP Post and HTTP/100 (continue) > > > > > > > Simon > > > There's only one possible cause of the problem I can think of at the > > > moment is not flushing the output stream. If my assumption proves wrong, > > > I'll be left completely clueless. What OS are you using, btw? Somehow, I > > > have an impression that the problem is platform dependent. > > > Oleg > > > > > > > > > > > > On Tue, 2003-02-25 at 23:17, Simon Roberts wrote: > > > > Attached is a log of my application (log4j, with most of the > > > > HttpConnection.isResponseAvaliable messages removed) > > > > > > > > BTW: typo in method name > > > > > > > > The interesting bit is that it times out (3 seconds) rather than getting > > the > > > > 100-continue response. Then, after it has send the body, the > > 100-continue > > > > response is received and returned (which is what is actually causing my > > > > problem). The server is a current release version of Jetty > > > > http://jetty.mortbay.org/jetty/ which appears to be working perfectly in > > all > > > > other regards. > > > > > > > > I get the same problem with HTTP PUT. > > > > > > > > Adding > > > > > > > > method.setUseExpectHeader(false); > > > > > > > > seems to fix it. > > > > > > > > Cheers, Simon > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Oleg Kalnichevski" <[EMAIL PROTECTED]> > > > > To: "Commons HttpClient Project" > > <[EMAIL PROTECTED]> > > > > Cc: "Simon Roberts" <[EMAIL PROTECTED]> > > > > Sent: Tuesday, February 25, 2003 10:18 PM > > > > Subject: Re: HTTP Post and HTTP/100 (continue) > > > > > > > > > > > > > Simon > > > > > I'd really appreciate it if you could send us the debug trace for > > > > > analysis. Please refer to the following url for instructions on how > > wire > > > > > log can be activated: > > > > > > > > > > http://jakarta.apache.org/commons/httpclient/logging.html > > > > > > > > > > Your problem should be easily solvable by disabling "100-continue" > > > > > handshake. > > > > > > > > > > PostMethod myhttppost = new PostMethod(); > > > > > myhttppost.setUseExpectHeader(false); > > > > > > > > > > Cheers > > > > > > > > > > Oleg > > > > > > > > > > > > > > > On Tue, 2003-02-25 at 00:29, Simon Roberts wrote: > > > > > > Gidday, > > > > > > > > > > > > This is probably a dumb-user question, but if it is, then it might > > need > > > > to > > > > > > be documented for other dumb users :) > > > > > > > > > > > > I just checked out the latest CVS HttpClient and tried it with my > > > > > > application (it's using HEAD from a month or two ago), and am having > > a > > > > > > problem. > > > > > > > > > > > > Our app does HTTP POST (to a Jetty server, as it happens). > > Previously, > > > > > > httpclient used to just push the request header and body along in > > one > > > > lump, > > > > > > and when the server posted a http-100 (continue) status, it used to > > > > complain > > > > > > about "continue received, but body already sent". Anyway, it used > > to > > > > work > > > > > > okay for us... > > > > > > > > > > > > Now, the httpClient.execute(method) returns 100, and there is no > > > > response > > > > > > (body) from the server, so my app barfs. > > > > > > > > > > > > The question is, how do I make httpclient send the body of the > > request? > > > > > > (maybe after I get the 100 back). > > > > > > > > > > > > Cheers, thanks, Simon > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: > > > > [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: > > > > [EMAIL PROTECTED] > > > > > For additional commands, e-mail: > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
