This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3k
npm login fails on password w/special characters #5729
Labels
Comments
This falls under #5782 now. |
Seems to be fixed on 1.4 and master. |
isaacs
added a commit
to npm/npm-registry-client
that referenced
this issue
Aug 22, 2014
A password like '%1234' would be broken and interpreted as '\u000034' in the request, becuase it is interpreting the %12 as a percent-encoded hex, and then it gets broken in the conversion to UTF-8. Fix npm/npm#6008 Fix npm/npm#5729 Fix npm/npm#5772 Fix npm/npm#5682 Related to npm/npm#5782, but not a fix, since that issue is asking for the npm client and website to have the *same* set of rules, and this commit does not guarantee that that is the case.
isaacs
added a commit
to npm/npm-registry-client
that referenced
this issue
Aug 22, 2014
A password like '%1234' would be broken and interpreted as '\u000034' in the request, becuase it is interpreting the %12 as a percent-encoded hex, and then it gets broken in the conversion to UTF-8. Fix npm/npm#6008 Fix npm/npm#5729 Fix npm/npm#5772 Fix npm/npm#5682 Related to npm/npm#5782, but not a fix, since that issue is asking for the npm client and website to have the *same* set of rules, and this commit does not guarantee that that is the case. Forward-ported from the fix on the v2.0 branch: 62f04f0
I am having this issue where my password contains
|
Had the same issue here. My password had a carrot (^) and dollar sign ($) in it and I was unable to login via
Here's the output:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While trying to "npm login" on a new machine, I was unable to complete the process. The username and password are correct (they work just fine on the website), but no luck. However, by changing my password to one that does not contain any of the special characters below, "npm login" works just fine.
The password that caused the issues (which is no longer in use, in favor of one I can npm login with) contained %, #, and ^ (as well as an assortment of alphanumerics, of course).
Console output and npm-debug.log are at https://gist.github.com/todesschaf/78a546787b19223ba40b
The text was updated successfully, but these errors were encountered: