🐛 BUG: `wrangler pages dev` throws 404 for URL with unicode character
See original GitHub issueWhat version of Wrangler
are you using?
2.0.15
(edit: issue persists in 2.0.24)
What operating system are you using?
Linux
Describe the Bug
A directory with name ń
(%C5%84
) is served correctly with wrangler pages publish
,
but throws a 404 when accessed with wrangler pages dev
.
Issue Analytics
- State:
- Created a year ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
Unicode characters causing 404 error in file_get_contents()
It returns 404 error. If I visit that URL in the browser, it's fine, because the browser replaces ó to %C3%B3.
Read more >wrangler 1.19.13
[Scrumpyy], [pull/2208]** The previous URL specified ( https://developers.cloudflare.com/workers/tooling/wrangler/install/ ) leads to a 404 page that was ...
Read more >Gatsby site: Non-latin URLs give 404 error - Workers
So perhaps the error happens because it looks for the encoded URL above, and I store the decoded URL. BUT, if I store...
Read more >Table 11 :: OIN Linux System
Am-utils includes many additional updates, ports, programs, features (such as NFS V.3 support and shared libraries), bug fixes, and more.
Read more >Untitled
Walker crab orchard wv, Ti 84 calculator games mario, Partial page refresh in ... Kruti dev to unicode font converter online, Jus soli...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue seems to be present for ALL filenames that are url-encoded? Even files with spaces in the names 404.
After some testing, this is not a wrangler issue, but instead a miniflare issue. I have created an issue on their repo, and would recommend you follow that instead 🙂