quote
Some servers (IIS) require the client to use chunked file transfer
encoding to transfer files larger than 2G. If you are not using
chunked try that
Could you point me to an example of how to specify to use chunked file
transfer with HttpClient on a GET request?
--
View this message
On Thu, 2008-03-06 at 19:42 +0100, Tov Are Jacobsen wrote:
Hi,
I'm getting a warning and an Exception stack-trace for every single
connection I do after the first one.
I consumeContent after each request, so I think my code should be ok
... and it works as well, but I wonder
if it's
On Fri, 2008-03-07 at 13:24 +0800, micky wrote:
Dear,
I finally figure out how to log!!
Please help me find out why these two connections' cookie are different.
Because HttpClient does not find the first cookie when executing the
second request. You are not creating a new instance of
I thought about that, yet in this situation neither the Type 1 nor the
Type 2 message includes the Negotiate_NTLM2_Key flag.
However, when firefox or IE talks to the same proxy, the type 1
message includes Negotiate_NTLM2_Key as does the type 2 message.
If the proxy were required to use NTLM2,
sjlucas wrote:
Could you point me to an example of how to specify to use chunked file
transfer with HttpClient on a GET request?
It should be the default if you are connecting to the server
using HTTP/1.1. Chunked encoding does not exist in HTTP/1.0.
hope that helps,
Roland
Hello Micky,
what you are referring to is a trust store. Having a secure
connection without knowing that it points to the correct
recipient is completely pointless. Instead of eavesdropping
on the connection, everybody could just pretend to be the
recipient and receive the data directly. No,
