t ;)
>
> -Original Message-
> From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 29, 2004 3:56 PM
> To: Commons HttpClient Project
> Subject: RE: streaming responses
>
>
> Bob,
>
> "Buffering response body"
s,
> Bob
>
> -Original Message-
> From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 29, 2004 3:04 PM
> To: Commons HttpClient Project
> Subject: Re: streaming responses
>
>
> Bob,
>
> There's no special magic invo
> From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 29, 2004 3:04 PM
> To: Commons HttpClient Project
> Subject: Re: streaming responses
>
>
> Bob,
>
> There's no special magic involved. Make sure you use
> HttpMethod#getResponseBo
ly misreading the signs?
Thanks,
Bob
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 29, 2004 3:04 PM
To: Commons HttpClient Project
Subject: Re: streaming responses
Bob,
There's no special magic involved. Make sure you use
HttpMe
Bob,
There's no special magic involved. Make sure you use
HttpMethod#getResponseBodyAsStream, which will return the raw input
stream, and not its buffering counterparts
HttpMethod#getResponseBodyAsString and HttpMethod#getResponseBody.
You should not worry about chunking. HttpClient will decode c
Howdy,
I've just started using HttpClient for testing. The product that I am
developing includes a software download feature that downloads (sometimes
very large) files over the internet using HTTP. The reason we use HTTP is
that many of our customers are unwilling to open their proxies or firew
