OK, I have the proxy working.
Now I think I have a redirect problem. I've read in the documentation
HttpClient automatically handles redirects however I'm getting response which
looks like this:
302 Found
Found
The document has moved https://www.server.com/path/";>here.
David,
Adding "Accept" header works..
Thanks,
Sudeep
-Original Message-
From: David Motes [mailto:davidmo...@gmail.com]
Sent: Friday, September 09, 2011 10:43 AM
To: HttpClient User Discussion
Subject: Re: Transfer Encoding chunked
Is the resource you are trying to get some kind of m
Is the resource you are trying to get some kind of media file? Like
audio, video, etc?
It is probably the Accept: */* header. Try adding the Accept header
and see what happens.
On Fri, Sep 9, 2011 at 1:34 PM, sebb wrote:
> On 9 September 2011 18:08, Sudeep Pradhan wrote:
>> But why does th
On 9 September 2011 18:08, Sudeep Pradhan wrote:
> But why does the same HTTP GET request work with curl. What is the difference?
>
> I get the correct chunked response with curl 7.21.6. I have posted the curl
> "wire log" in the previous email.
The curl response includes
Transfer-Encoding: chu
But why does the same HTTP GET request work with curl. What is the difference?
I get the correct chunked response with curl 7.21.6. I have posted the curl
"wire log" in the previous email.
Thanks,
Sudeep
-Original Message-
From: Sam Crawford [mailto:samcrawf...@gmail.com]
Sent: Friday
On Fri, 2011-09-09 at 07:32 -0700, Michael Remijan wrote:
> Unfortunately, the proxy connection is still not working. I'm in the
> position where I guess I have to use an NTLM proxy. This proxy does not
> require authentication (for example, I can configure my web browser to point
> to proxy.s
Unfortunately, the proxy connection is still not working. I'm in the position
where I guess I have to use an NTLM proxy. This proxy does not require
authentication (for example, I can configure my web browser to point to
proxy.server.com:8080 and the web browser connects fine) However, whenev
Your issue is not related to transfer-encoding. The wire log you have
doesn't show "Transfer-Encoding: Chunked" as a response header. But it
does show this important line:
2011/09/08 16:08:13:433 PDT [DEBUG] headers - << Content-Length: 0
This says that the server is replying with no body after t