You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by bu...@apache.org on 2003/05/08 18:41:28 UTC
DO NOT REPLY [Bug 19771] New: -
Netscape proxy problem wtih POST
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=19771>.
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=19771
Netscape proxy problem wtih POST
Summary: Netscape proxy problem wtih POST
Product: Commons
Version: Nightly Builds
Platform: PC
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: HttpClient
AssignedTo: commons-httpclient-dev@jakarta.apache.org
ReportedBy: bin.chen@sabre-holdings.com
Description:
When using httpClient to POST to a http url through a Netscape proxy server,
the httpClient failed due to read error when reading status line. The log seem
to indicate that the proxy is talking HTTP/1.0 and does not expect the POST
data to come. I am using a modified version of the ClientApp from examples. I
will attach both the test program and log files.
Workaround:
If use PostMethod.setUseExpect (true), it will work. But in many cases, it
would be slower.
Related issues:
In doing the test, I also found out that the httpClient PostMehtod does not
work when the request body is NOT set (not calling setRequestBody). It also
does not work with empty body (setRequestBody ("")). The attached
clientApp.properties file has flags to test each case and I will attach the
logs as well. Excuse my ignorance, I do not know for sure what the HTTP spec.
says about the body in the POST method. But at least if the caller/app is
wrong in not setting the body, some exception should be thrown. It could also
be my server's problem, please let me know if that is the case (I am using
weblogic server 6.1).