➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jesstess
Recipients BreamoreBoy, gregory.p.smith, jan.kollhof, jesstess, jjlee, orsenthil
Date 2013-04-13.21:13:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365887626.82.0.485235234875.issue4140@psf.upfronthosting.co.za>
In-reply-to
Content 
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 file and not a diff, but I think from the transcript in msg74918 that Jan is discussing the format of the digest-uri header. That field is in turn defined in RFC 2616, section 5.1.2: Request-URI.

    Request-URI    = "*" | absoluteURI | abs_path | authority

    The absoluteURI form is REQUIRED when the request is being made to a
   proxy.

So I believe urllib2 has the correct, RFC-conforming behavior here by sending the full URI through a proxy, and the issue is with IIS.

Thus, I recommend that we close this ticket as invalid.
History
Date User Action Args
2013-04-13 21:13:46jesstesssetrecipients: + jesstess, gregory.p.smith, jjlee, orsenthil, jan.kollhof, BreamoreBoy
2013-04-13 21:13:46jesstesssetmessageid: <1365887626.82.0.485235234875.issue4140@psf.upfronthosting.co.za>
2013-04-13 21:13:46jesstesslinkissue4140 messages
2013-04-13 21:13:46jesstesscreate