[issue4140] urllib2: request with digest auth through proxy fail

Senthil Kumaran added the comment: Yes, RFC specifically states that "The absoluteURI form is REQUIRED when the request is being made to a proxy." Thanks Jessica for making a note of that. Closing this issue as Invalid. -- dependencies: -urllib2 fails against IIS 6.0 (No support for M

[issue4140] urllib2: request with digest auth through proxy fail

Jessica McKellar added the comment: jan.kollhof, thanks for the report and your work on this ticket! The format of the client response to a server's digest challenge is detailed in RFC 2617, section 3.2.2: The Authorization Request Header. The urllib2.py attachment is unfortunately the whole f

[issue4140] urllib2: request with digest auth through proxy fail

Senthil Kumaran added the comment: This might be related to issue2202 as well. -- assignee: gregory.p.smith -> orsenthil dependencies: +urllib2 fails against IIS 6.0 (No support for MD5-sess auth) nosy: +orsenthil resolution: -> accepted ___ Python

[issue4140] urllib2: request with digest auth through proxy fail

Mark Lawrence added the comment: As it's not actually known whether urllib2 or IIS is at fault, I suggest this is closed, it can always be reopened. -- nosy: +BreamoreBoy ___ Python tracker ___

[issue4140] urllib2: request with digest auth through proxy fail

Changes by Daniel Diniz : -- nosy: +jjlee ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue4140] urllib2: request with digest auth through proxy fail

Changes by Daniel Diniz : -- stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue4140] urllib2: request with digest auth through proxy fail

Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- assignee: -> gregory.p.smith nosy: +gregory.p.smith priority: -> normal versions: +Python 2.7, Python 3.1 -Python 2.5 ___ Python tracker <[EMAIL PROTECTED]> _

[issue4140] urllib2: request with digest auth through proxy fail

New submission from Jan-Klaas Kollhof <[EMAIL PROTECTED]>: When using a proxy to request URLs that require Digest Auth, a header similar to the following is sent to the server: Authorization: Digest ... uri="http://example.org/foobar/spam"; ... The server then responded with: HTTP/1.1 400 Bad