You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Confirmed. There are workarounds for this documented in nodejs/node#1693, and developers really ought not be passing non-ascii characters into the headers but writeHead should be operating defensively here and it's not. This ought to get fixed but since there are good workarounds it's likely not a high priority.
Node versions affected: Tested on v0.12.2
Platforms affected: Tested on mac, should apply to all platforms
High priority/critical category: No
recommended priority: P3
Existing io.js issue: nodejs/node#1693
Pull request included: No
Reproducible: Yes
Exists in later version: Not yet tested in v0.10
@joyent/node-coreteam
To reproduce this bug, execute the code below and open http://localhost:777/ in the browser. This page redirects to a page from the location header, and browser should open http://localhost:777/?text=что-то%20русское .
In node.js version 0.10.15 and earlier, it works fine, but in the latest version, node.js opens the http://localhost:777/?text=GB>-B>%20@CAA:>5 url.
I think that the issue is linked to the writeHead function that incorrectly encodes headers and sends them to the browser.
The text was updated successfully, but these errors were encountered: