Open GoogleCodeExporter opened 9 years ago
In the svn trunk, the details of HTTP transport have been abstracted so that
users can choose to do things like this (choose curl over internal http
implementation, etc). Have you tried trunk with a curl based HTTP transport set?
I'm not sure from the curl documentation whether it necessary for you to set
the encoding option - i think it defaults to sending all supported encodings:
"The contents of the "Accept-Encoding: " header. This enables decoding of the
response. Supported encodings are "identity", "deflate", and "gzip". If an
empty string, "", is set, a header containing all supported encoding types is
sent."
I'll try to take a look into this and confirm / deny whether the proper headers
for gzip / deflate are sent by default - if not I'll add the option to the
trunk implementations.
Original comment by donovan....@gmail.com
on 8 Mar 2011 at 6:07
Hey Donovan,
I studied the change in the current trunk, the http transport abstraction is a
pretty cool thing.
I guess it is the right way to implement stuff like this for a general purpose
(composite > inheritance).
I tried to remove the curl encoding option, but then the response is 1-2MB
again. With the
"gzip, deflate" or the empty string "" it is just a tenth of it. In my opinion
curl sends no encoding
header as default and that is like "identity".
cheers,
Rafael.
Original comment by schlende...@gmx.net
on 9 Mar 2011 at 9:55
Hi to use this ? What options/settings did you tweak in jetty/solr ?
Original comment by Jacque...@gmail.com
on 19 May 2011 at 2:03
Hi,
there is nothing special to do. "Deflate" should be enabled by default in
Tomcat.
Cheers,
Rafael.
Original comment by schlende...@gmx.net
on 19 May 2011 at 7:04
Original issue reported on code.google.com by
schlende...@gmx.net
on 8 Mar 2011 at 5:43Attachments: