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=36918>. 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=36918 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-05 11:25 ------- (In reply to comment #4) ... > Oleg, > See below for similar headers for a non-SSL connection. It's like "/stuff" > though I'm not sure if that is strictly RFC compliant or not. Tommorrow I'll > try a few variations and see if anything interesting happens. > So, the situation is far from being simple. There's no consistency in how various HTTP agents and servers handle the digest-uri. I re-read the RFC and this did not make things any clearer for me. There are ways of seeing and not seeing, depending on what one wants or does not want to see. Hence, the inconsistency in implementations I suggest the following: (1) For release 3.0 we basically do nothing because we simply can't work around the problem without unfreezing the API (2) For release 3.1 we can fix the problem for CONNECT methods. This can be done without breaking the 3.x API comatibility (3) We revisit the problem in the course of 4.0 development and try to come up with a proper fix for the problem Oleg -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
