Skip to content

Incorrect quoting in Content-Disposition headers? #520

@catlee

Description

@catlee

I've having a hard time grokking the various RFCs, but I just came across a service that refused to parse Content-Disposition lines like this:

CONTENT-DISPOSITION: form-data; name=file; filename="upload.gpx"; filename*=utf-8''upload.gpx

But accepted this:

CONTENT-DISPOSITION: form-data; name="file"; filename="upload.gpx"; filename*=utf-8''upload.gpx

The only difference being the quoting of the name parameter. Is aiohttp doing the right thing here? Is there a way to force quoting to happen?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions