urllib2: correct way how to add a header to the *initial* request?
Matěj Cepl
mcepl at redhat.com
Sat Feb 8 12:29:19 EST 2014
More information about the Python-list mailing list
Sat Feb 8 12:29:19 EST 2014
- Previous message (by thread): urllib2: correct way how to add a header to the *initial* request?
- Next message (by thread): Python3, __slots__ and serialization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, this is probably a dumb question but I just cannot find a way how to create AuthHandler which would add Authorization header to the FIRST request. The only thing I see in urllib2.py are various http_error handler which add Authorization header to the ADDITIONAL request which handles the error. However, when looking at http://www.ietf.org/rfc/rfc2617.txt, section 2, I see this: A client MAY preemptively send the corresponding Authorization header with requests for resources in that space without receipt of another challenge from the server. And really many servers (e.g., api.github.com) expect the Authorization header to be sent with the initial request, and actually they broken (http://developer.github.com/v3/auth/#basic-authentication) so instead of 401 they send 404 status code. Anybody has any idea how to subclass *AuthHandler so that it would add the header on the initial request? Best, Matěj -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 190 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-list/attachments/20140208/191a63ab/attachment.sig>
- Previous message (by thread): urllib2: correct way how to add a header to the *initial* request?
- Next message (by thread): Python3, __slots__ and serialization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list