|
Mantis - Hessian
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5497 | feature | always | 08-14-13 02:45 | 08-14-13 02:45 | |
|
|
|||||
| Reporter: | JoergV | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 4.0.28 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
|
|
|||||
| Summary: | 0005497: Support for GZIP compression | ||||
| Description: |
This is a very similiar request as: http://bugs.caucho.com/view.php?id=4151 [^] The best compression choice for http compression is "gzip". Taken from Wikipedia: http://en.wikipedia.org/wiki/HTTP_compression [^] 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.[5][6] 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: | |||||
| Additional Information: |
A possible solution: HessianProxy.java: conn.addHeader("Accept-Encoding", "gzip, deflate"); HessianURLConnection.java: if ("gzip".equals(contentEncoding)) { return new GZIPInputStream(_conn.getInputStream()); } return _conn.getInputStream(); |
||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |