|Anonymous | Login | Signup for a new account||12-14-2019 11:17 PST|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0005497||[Hessian]||feature||always||08-14-13 02:45||08-14-13 02:45|
|ETA||none||Fixed in Version||Product Version||4.0.28|
|Summary||0005497: Support for GZIP compression|
This is a very similiar request as:
The best compression choice for http compression is "gzip".
Taken from Wikipedia:
deflate - despite its name the zlib compression (RFC 1950) should be used (in combination with the deflate compression (RFC 1951)) as described in the RFC 2616. The implementation in the real world however seems to vary between the zlib compression and the (raw) deflate compression. Due to this confusion, gzip has positioned itself as the more reliable default method (March 2011).
It would be great if "Accept-Encoding" would be extended to "gzip, deflate" and both encodings would be supported. This can be archived with just a couple of lines.
|Steps To Reproduce|
A possible solution:
conn.addHeader("Accept-Encoding", "gzip, deflate");
return new GZIPInputStream(_conn.getInputStream());
|There are no notes attached to this issue.|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed.|
24 unique queries executed.