Skip to content

[Bug]: URL encoded space in path causes ___netlify-handler function to 502 #786

Closed
@chrishannaby

Description

@chrishannaby

Steps to reproduce

For a site using v4 of the plugin if you try to navigate to the a path that contains a URL encoded space character i.e. %20 the ___netlify-handler deployed by the plugin returns a 502 error. You can see a live example of this here:

https://next-kitchensink-starter.netlify.app/hello%20world

Which returns this error:

{"errorType":"TypeError","errorMessage":"Request path contains unescaped characters","trace":["TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters","    at new ClientRequest (_http_client.js:147:13)","    at request (http.js:46:10)","    at /var/task/.netlify/functions-internal/___netlify-handler/bridge.js:169:19","    at new Promise (<anonymous>)","    at Bridge.launcher (/var/task/.netlify/functions-internal/___netlify-handler/bridge.js:167:12)","    at async Runtime.handler (/var/task/.netlify/functions-internal/___netlify-handler/___netlify-handler.js:123:40)"]}

Tested with @netlify/plugin-nextjs@4.0.0-beta.6

A link to a reproduction repository

https://github.com/chrishannaby/next-starter

More information about your build

  • I am building using the CLI
  • I am building using file-based configuration (netlify.toml)

What OS are you using?

Mac OS

Your netlify.toml file

[build]
publish = ".next"

[[plugins]]
package = "@netlify/plugin-nextjs"

Relevant log output (or link to your logs)

No response

Metadata

Metadata

Assignees

Labels

type: bugcode to address defects in shipped code

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions