Oleg,
Point well taken. I found out, as you pointed out, that handling the
authentication manually with HttpClient 2.0 is not as easy (or as
ideal) as I had hoped.
I have decided to go the 'expect-continue' route.
Thanks everyone for your help with this,
Jen
On Jul 14, 2004, at 11:43 AM, Oleg Ka
On Wed, 2004-07-14 at 18:10, Jennifer Ward wrote:
> On Jul 13, 2004, at 8:03 PM, Michael Becke wrote:
>
> >
> > Another way to handle this problem is to use the "expect 100 continue"
> > feature of HTTP. This feature is disabled in HttpClient by default,
> > as only a few servers support it cor
On Jul 13, 2004, at 8:03 PM, Michael Becke wrote:
Another way to handle this problem is to use the "expect 100 continue"
feature of HTTP. This feature is disabled in HttpClient by default,
as only a few servers support it correctly. You can re-enable it by
calling setUseExpectHeader(true) on t
Hello Jen,
Another way to handle this problem is to use the "expect 100 continue"
feature of HTTP. This feature is disabled in HttpClient by default, as
only a few servers support it correctly. You can re-enable it by
calling setUseExpectHeader(true) on the post method.
Mike
On Jul 13, 2004,
Yes, setting CONTENT_LENGTH_AUTO does buffer the content. However, in
doing this I realized it's not really the best solution since the
content will get sent twice (although, it gets ignored the first time).
So, it's not efficient.
In retrospect what I really want to do is establish the connect
Yes, HttpClient will buffer the content if you use CONTENT_LENGTH_AUTO.
Mike
On Jul 13, 2004, at 3:20 AM, Ingo Brunberg wrote:
The problem is that you are using chunked transfer encoding. This
prevents Httpclient to automatically buffer the content in memory and
the InputStream can only be read onc
Jennifer,
I just recently had to respond to a very similar question.
http://marc.theaimsgroup.com/?l=httpclient-commons-dev&m=108940676906963&w=2
To recap, whenever request body is streamed out (read directly from an
input stream) the request cannot be _automatically_ repeated.
There are three
Thanks for the reply. Unfortunately, I tried setting the Content-Length
header (no chunked transfer encoding), but that didn't work either.
I would appreciate any other suggestions you may have.
Sincerely,
Jennifer Ward
On Jul 13, 2004, at 12:20 AM, Ingo Brunberg wrote:
The problem is that you ar
The problem is that you are using chunked transfer encoding. This
prevents Httpclient to automatically buffer the content in memory and
the InputStream can only be read once.
The workaround is simply to provide the exact content-length.
Ingo
> Hi,
>
> I wonder if anyone could offer a suggestion
Hi,
I wonder if anyone could offer a suggestion for getting around an
exception I'm seeing.
I am writing a load test client that sends requests to a webdav server.
I have a putMethod which does the following:
PutMethod method = new
PutMethod(URIUtil.encodePathQuery(path
10 matches
Mail list logo
