➜
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.
Created on 2016-03-10 11:04 by Olivier.Le.Moign, last changed 2022-04-11 14:58 by admin.
| Messages (3) | |||
|---|---|---|---|
| msg261491 - (view) | Author: Olivier Le Moign (Olivier.Le.Moign) | Date: 2016-03-10 11:04 | |
According to RFC5987 (http://tools.ietf.org/html/rfc5987), it's possible to use other encoding than ASCII in header fields. Specifically in the CGI library, posting files with non-ASCII characters will lead the header to be (for example) filename*=utf-8"xxxxx" which is not recognised: l 513 if 'filename' in pdict: self.filename = pdict['filename'] self._binary_file = self.filename is not None The file will thus be treated as a string. The correction isn't too big but being a total newbie, I'm a bit scared to suggest a patch. |
|||
| msg261492 - (view) | Author: Olivier Le Moign (Olivier.Le.Moign) | Date: 2016-03-10 11:12 | |
I guess this is fixed by https://pypi.python.org/pypi/rfc6266. Could have looked better, sorry. |
|||
| msg364787 - (view) | Author: Martin Panter (martin.panter) *  |
Date: 2020-03-22 06:01 | |
I’m not an expert on the topic, but it sounds like this might be a duplicate of Issue 23434, which has more discussion. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:28 | admin | set | status: pending -> open github: 70714 |
| 2020-03-22 06:01:40 | martin.panter | set | status: open -> pending nosy: + martin.panter messages: + msg364787 superseder: support encoded filename in Content-Disposition for HTTP in cgi.FieldStorage resolution: duplicate |
| 2016-03-10 11:12:02 | Olivier.Le.Moign | set | messages: + msg261492 |
| 2016-03-10 11:04:31 | Olivier.Le.Moign | create | |