-
Notifications
You must be signed in to change notification settings - Fork 98
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
Problems with UTF characters #205
Comments
abubakriz
added a commit
to abubakriz/serve-handler
that referenced
this issue
Jul 31, 2024
When a file url has certain symbols like number sign (#), it doesn't encode them, which makes the browser fail to navigate to the file, thinking it is a document section. This commit fixes that by encoding urls using the built-in encodeURIComponent function. Fixes vercel#120, vercel#205, vercel/serve#726, and vercel/serve#774
7 tasks
Some of the issues over at Curiously, the Try serving a static file named As a workaround, I'm currently doing: return serveHandler(request, response, {
headers: [
{
source: '**/*',
headers: [
{
key: 'Content-Disposition',
value: '',
},
],
},
],
}) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think serve-handler isn't implementing RFC 5987 correctly.
When I attempt to serve a file with the name
DALL·E 2024-01-17.png
(note the bullet point) I get the following error:I put together a minimal demo
The text was updated successfully, but these errors were encountered: