Skip to content

Provide support for encoded (Content-Disposition) header #1001

@cl-weclapp

Description

@cl-weclapp

We're using an encoded Content-Disposition-header as specified in RFC 5987.

Example:
Content-Disposition: attachment; filename*=UTF-8''example.pdf

The header is not interpreted correctly and the download of documents fails ("Response Status: Cannot read properties of undefined (reading 'replace') (CORS or Network Issue)"). We're loving rapi-doc and with the support of the encoded headers we would be completely happy :-)

Thanks in advance

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions