I think I'm pretty certain it is #1.

I'm going to check in fixes to this into both the branch and into
trunk, and flag the HTTPCLIENT-1315 ticket also as being potentially
fixed, since this could easily be the problem with that situation as
well.

Karl


On Sun, Feb 17, 2013 at 11:32 AM, Jason Millard <[email protected]> wrote:
> Hello.
>
> Good news! I just tested the latest JAR and I'm glad to say it works
> great. I was able to retrieve the URL and receive a 200!
>
> Do you need any more wireshark logs to verify which fix 1 or 2 was the 
> culprit?
>
> -- Jason

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to