This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
Add user does not work #70
Labels
Comments
This is true. I have a fix in mind and it's pretty easy to implement, so I'll probably get that out today and include it in |
Great, thanks! |
Here is another example of a not working non-root registry. Please consider this in your fix. Thanks! |
This is actually a bit more involved than I originally thought it was, but my current goal is to get this into |
othiym23
added a commit
to npm/npm
that referenced
this issue
Oct 24, 2014
Fixes npm/npm-registry-client#77, partially addresses npm/npm-registry-client#70.
This was referenced Oct 24, 2014
othiym23
added a commit
to npm/npm
that referenced
this issue
Oct 31, 2014
Fixes npm/npm-registry-client#77, partially addresses npm/npm-registry-client#70.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am experiencing the same issue as described in npm/npm-registry-couchapp#199. The issue is caused by the changes in npm-registry-client/lib/adduser.js done in the commit c96fc63. There
url.resolve()
is used to replacerequest.toRegistryURL()
, so that the path segments of the registry URL get truncated. For instance, in case of npm-registry-couchapp, the base URL has the shape ofhttp://host:port/registry/_design/app/_rewirte
. After applyingurl.resolve()
, the request URL looks likehttp://host:port/-/user/org.couchdb.user:*
, which is rejected by CouchDB, since the dash sign in the URL is recognized as a database name which is not allowed in CouchDB.Configuring a virtual host in CouchDB for the npm-registry-couchapp is not always an option.
The text was updated successfully, but these errors were encountered: