Adrian Sutton wrote:
Odi,
most likely I will have to spend a few days in Düsseldorf next week, but I'll
do my best to organize my trip in a way that can make it to the party. 2.0
release is definitely worth celebrating as far as I am concerned.
Oleg
And I'll most likely be toasting the
This may be getting fixed soon. See the bugtrack item for Jetty:
http://sourceforge.net/tracker/index.php?func=detailaid=699011group_id=732
2atid=107322
The item remains open, and greg is normally pretty good about closing things
when they're done.
Cheers, Simon
- Original Message -
Carl,
That's OK, the problem
I run into is that after running for not very long, I suddenly start
getting
everything timing out. It's hard to really pinpoint the timing, giving all
the
activity, and no thread identifiers in the log messages, but I think what
is
happening is that the
Oleg,
The 'expect: 100-continue' related code has been significantly refactored
I am no longer experiencing the timeout problem (everything works well when
sending the expect-100 header).
However, my HTTP server (Jetty) seems to be still sending HTTP/1.1 100
Continue when the Expect header is
I'm am following this up with the Jetty community.
Keep me in the feedback loop, though. If there's anything I could help
Jetty folks with, just let me know
FYI
http://sourceforge.net/tracker/index.php?func=detailaid=699011group_id=732
2atid=107322
);
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
Yes, but you have done a very bad thing here. By doing the
executeMethod(), you have established a connection to the server, and
have read the headers. But then you are closing the connection before
reading the body. The client (thats you!) is responsible for completing
the read by
