DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=14036>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=14036 MultipartPostMethod does not check for error messages ------- Additional Comments From [EMAIL PROTECTED] 2004-09-27 18:44 ------- Mike, There are certainly real-life cases when this might be quite useful. Consider the following situation: the user executes a POST or a PUT with a large request entity against a protected URL providing no or invalid credentials. The target server reads the request headers, fails to authenticate the user, and immediately drops the connection without reading the request body. HttpClient happily goes on writing the request body until it gets IOExcpetion "socket closed". The server response never gets parsed. Instead of expected status code SC_UNAUTHORIZED the user gets a misleading IOException. Even the most Httpclient savvy users may be left wondering as to what is the cause of the problem. To make matters worse, HttpClient will attempt to retry the method a few times before giving up This said, there are better ways to deal with the problem. Expect-Continue is one. Executing a test GET or HEAD against the target URL to ensure authorization is another. Since we are both in agreement that the extra complexity does not appear to buy a lot I suggest the issue be marked as WORNTFIX. If there are strong objections or additional input in favor of the patch, the bug report can always be reopened. What do you think? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
