|Anonymous | Login | Signup for a new account||11-25-2020 11:19 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|
|0003579||[Hessian]||major||always||06-25-09 19:43||08-28-09 08:51|
|ETA||none||Fixed in Version||4.0.1||Product Version||4.0.0|
|Summary||0003579: v1.0 requests seem to result in transfer-coding chunk size of 1 byte, dramatically increasing payload size|
I'm experiencing a situation where making a v1.0 request against my Hessian service results in half of the response being sent in single-byte chunks. This at least doubles that portion of the payload, since HTTP requires a chunk length byte for every chunk.
Test code that fetches using the 3.2.1 hessian Java library, and presumably uses 2.0, behaves much better in this regard. The 1.0 client code is HessianKit (Objective C), used on the iPhone.
|Steps To Reproduce|
|There are no notes attached to this issue.|
|06-25-09 19:43||rmann||New Issue|
|07-03-09 01:16||rmann||Issue Monitored: rmann|
|08-28-09 08:51||ferg||Assigned To||=> ferg|
|08-28-09 08:51||ferg||Status||new => closed|
|08-28-09 08:51||ferg||Resolution||open => fixed|
|08-28-09 08:51||ferg||Fixed in Version||=> 4.0.1|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.|
25 unique queries executed.