Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
cl-weclapp opened this issue Feb 9, 2024 · 0 comments
Closed

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

cl-weclapp opened this issue Feb 9, 2024 · 0 comments

Comments

@cl-weclapp
Copy link

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

@mrin9 mrin9 closed this as completed in 5362b26 Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant