> Sorry, I don't have that post. It's not in my local mailbox, nor
can I find it in the mailing list archives. You have posted on
Dec 1st, then again on Dec 4th. Maybe your mail was rejected by
the mailing list server because of attachments?
My mistake, the post was stuck in Nabble. Have resent it, let me know if
you dont see it in your mail box.
>Have you tried my original suggestion and sent the request
with a header "Accept-Encoding: gzip" to allow the server to
compress the response? Of course you'll have to decompress
it again in your application.
At my client I do send the header "Accept-Encoding: gzip" by default (and
decompress the stream). But unfortunately, the server (Reuter's) is not
configured to send out compressed stream.
Thanks
--
View this message in context:
http://www.nabble.com/Performance-Issues-with-Transfer-Encoding-chunked-tp14106574p14401737.html
Sent from the HttpClient-User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
