Julien ÉLIE <[email protected]> added the comment:
David: no, the RFC does not mention UTF-8 about AUTHINFO.
Please note the subtlety:
command =/ authinfo-sasl-command /
authinfo-user-command /
authinfo-pass-command
authinfo-sasl-command = "AUTHINFO" WS "SASL" WS mechanism
[WS initial-response]
authinfo-user-command = "AUTHINFO" WS "USER" WS username
authinfo-pass-command = "AUTHINFO" WS "PASS" WS password
initial-response = base64-opt
username = 1*user-pass-char
password = 1*user-pass-char
user-pass-char = B-CHAR
; U- means based on UTF-8, excluding NUL CR and LF
; B- means based on bytes, excluding NUL CR and LF
U-CHAR = CTRL / TAB / SP / A-CHAR / UTF8-non-ascii
B-CHAR = CTRL / TAB / SP / %x21-FF
That is not for nothing that B-CHAR are explicitly mentioned. And *not* U-CHAR.
That is why I insist on that fact, and I fear the new nntplib implementation
using UTF-8 is breaking the NNTP protocol at some places...
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue10284>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
