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=16124>. 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=16124 isHttp11 should have HttpClient scope ------- Additional Comments From [EMAIL PROTECTED] 2004-04-30 08:55 ------- I am afraid I have to call back the patch, as there's a fundamental flaw in it. Consider the following scenario: * HttpConnection version is undefined (newly allocated connection) * The user executes a request using HTTP/1.0 (for whatever reason) * The connection will be marked as supporting HTTP/1.0 only * All consecutive requests on this connection will be forced to use HTTP/1.0 even though the connection may be perfectly capable of HTTP/1.1 or above I currently do not see a satisfactory solution to this problem with this approach. I have to think of something completely different. Bright ideas how to solve the problem of allowing for HttpConnection parameterization without giving the end user the direct access to the connection itself are welcome. I'll happily step aside Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
