-
Notifications
You must be signed in to change notification settings - Fork 27.7k
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
TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["Location"] #24047
Labels
Linking and Navigating
Related to Next.js linking (e.g., <Link>) and navigation.
Comments
This comment has been minimized.
This comment has been minimized.
2 tasks
10 tasks
timneutkens
added a commit
to timneutkens/next.js
that referenced
this issue
Jan 28, 2022
Fixes the merge conflicts in vercel#27003 Fixes vercel#24977 Fixes vercel#24047 Closes vercel#27003 Co-Authored-By: Jamie <[email protected]>
kodiakhq bot
pushed a commit
that referenced
this issue
Jan 28, 2022
Fixes the merge conflicts in #27003 Fixes #24977 Fixes #24047 Closes #27003 Co-Authored-By: Jamie <[email protected]> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`
natew
pushed a commit
to natew/next.js
that referenced
this issue
Feb 16, 2022
Fixes the merge conflicts in vercel#27003 Fixes vercel#24977 Fixes vercel#24047 Closes vercel#27003 Co-Authored-By: Jamie <[email protected]> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Next.js are you using?
10.1.3
What version of Node.js are you using?
15.14.0
What browser are you using?
Chrome, Firefox
What operating system are you using?
macOS
How are you deploying your application?
Other platform
Describe the Bug
While redirecting, application responds with Internal Server Error when sending request with invalid characters in query key.
Expected Behavior
Normal redirect is performed
To Reproduce
Send the request.
If
trailingSlash
is enabled,curl "http://localhost:3000/anypath?%E2%80%9D"
If
trailingSlash
is not enabled,curl "http://localhost:3000/anypath/?%E2%80%9D"
Internal Server Error
is returnedhttps://nodejs.org/api/http.html#http_response_setheader_name_value
The text was updated successfully, but these errors were encountered: