Senthil Kumaran orsent...@gmail.com added the comment:
This issue is Invalid. I am sorry that it had be open for so long
without any explanation.
The order in which the handlers are tried does not depend upon the way
http_error_auth_reqed method is coded, but rather on the handler_order.
In
Changes by Senthil orsent...@gmail.com:
--
assignee: - orsenthil
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1368312
___
___
Python-bugs-list
Changes by Daniel Diniz aja...@gmail.com:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1368312
___
___
Python-bugs-list
Changes by Daniel Diniz aja...@gmail.com:
--
nosy: +orsenthil
stage: - test needed
type: - behavior
versions: +Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1368312
___
Changes by Daniel Diniz aja...@gmail.com:
--
nosy: +jjlee
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1368312
___
___
Python-bugs-list mailing
david reid [EMAIL PROTECTED] added the comment:
I've run into this as an issue with a server that replies with both
digest and basic auth.
When parsing the keys in the header it's possible to detect the start of
a different auth method, so I'd suggest parsing the www-authenticate
line and
