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.

classification
Title: email.base64MIME.header_encode vs RFC 1522
Type: Stage:
Components: Library (Lib) Versions: Python 2.4
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: barry Nosy List: ajaksu2, barry, ucho
Priority: normal Keywords:

Created on 2005-01-17 14:45 by ucho, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg23974 - (view) Author: Ucho (ucho) Date: 2005-01-17 14:45
 i have a question about
email.base64MIME.header_encode. It returns something
like: =?iso-8859-2?b?. Shouldn't it be "B" instead "b"
? RFC 1522 says it can be only "Q" or "B"
msg81514 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2009-02-09 23:15
RFC 2047 says the encoding is case-insensitive. Please, close as invalid.

RFC 2047:
2. Syntax of encoded-words

   An 'encoded-word' is defined by the following ABNF grammar.
[...]
   encoded-word = "=?" charset "?" encoding "?" encoded-text "?="
   charset = token    ; see section 3
   encoding = token   ; see section 4

[...]
   Both 'encoding' and 'charset' names are case-independent.  Thus the
   charset name "ISO-8859-1" is equivalent to "iso-8859-1", and the
   encoding named "Q" may be spelled either "Q" or "q".
History
Date User Action Args
2022-04-11 14:56:09adminsetgithub: 41453
2009-02-11 23:05:28ajaksu2setstatus: open -> closed
resolution: not a bug
2009-02-09 23:15:20ajaksu2setnosy: + ajaksu2
messages: + msg81514
2005-01-17 14:45:16uchocreate