image optimizer returns 400 when path contains unicode characters #27210
Description
What version of Next.js are you using?
11.0.1
What version of Node.js are you using?
14.17.2
What browser are you using?
firefox
What operating system are you using?
ubuntu
How are you deploying your application?
vercel
Describe the Bug
in a production build, the image optimizer returns with status code 400, and error message "The requested resource isn't a valid image" when the image src contains non-ascii unicode characters.
Expected Behavior
image optimizer should handle paths with all allowed unicode characters
To Reproduce
- clone https://github.com/stefanprobst/issue-next-image-optimizer and
yarn install - run
yarn build && yarn start - there should be an image visible at http://localhost:3000, but there isn't. the network panel reports status code 400, error message "The requested resource isn't a valid image." which comes from here
- note that when running
yarn devthe image is visible