You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2002/04/15 05:47:36 UTC
DO NOT REPLY [Bug 8083] New: -
shouldn't automatically set Content-Length in request header
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8083>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8083
shouldn't automatically set Content-Length in request header
Summary: shouldn't automatically set Content-Length in request
header
Product: Commons
Version: Nightly Builds
Platform: Other
OS/Version: Other
Status: NEW
Severity: Critical
Priority: Other
Component: HttpClient
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: xiaowei@stratify.com
currently, httpclient automatically add Content-Length: 0 in the request
header, this is causing problems with some web servers, particularly, with
ar.atwola.com
Try the following URL
http://ar.atwola.com/file/adsWrapper.js
It will block indefinitely. This problem can be fixed by not sending the
Content-Length header, this is the browser's behavior. I'm not sure why this
casue problem, but let's conform to a standard browser's practice and avoid
troubles.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>