Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support rfc5987 filename in Content-Disposition

See original GitHub issue

See the filename* directive here. This directive is used to encode UTF-8 filenames as HTTP headers must only contain ASCII characters. Examples based on the RFC:

filename*=iso-8859-1'en'%A3%20rates
filename*=UTF-8''%c2%a3%20and%20%e2%82%ac%20rates

I think we can use this module to parse the directive.

Issue Analytics

State:
Created 6 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

2reactions

yassernasccommented, Jun 19, 2018

Trying to download a excel file, for example: https://www.cepea.esalq.usp.br/br/indicador/series/boi-gordo.aspx?id=2, I am getting the error TypeError: invalid parameter format.

1reaction

kevvacommented, May 26, 2017

Yeah, dead standard indeed. But unsure how often you encounter it. Anyway, I’m going to have a look at it and do a PR to them.

Top Results From Across the Web

Use of the Content-Disposition Header Field in the Hypertext ...

The "filename*" parameter (Section 4.3), using the encoding defined in [RFC5987], allows the server to transmit characters outside the ISO-8859-1 character set, ...

Encode filename according to rfc 5987 in python / tornado

From How to encode the filename parameter of Content-Disposition header in HTTP? I learnt that the encoding defined in RFC 5987 is used...

Content-Disposition - HTTP - MDN Web Docs

The parameters filename and filename* differ only in that filename* uses the encoding defined in RFC 5987. When both filename and filename* ...

Filename* parameter not supported in Content-Disposition ...

It looks like the multipart parser does not support extension notation (RFC 5987) for filename parameter. I am getting the following error: ...

Use of the Content-Disposition Header ... - greenbytes GmbH

HTTP/1.1 defines the Content-Disposition response header field, ... except that "filename*" uses the encoding defined in [RFC5987] , allowing the use of ...