You can reproduce it easily using curl or a web browser. If your username has an @ in it, you can't use URL authentication successfully even if you url encode the username.
On Tue, Aug 24, 2010 at 12:49 AM, Benoit Chesneau <[email protected]> wrote: > On Tue, Aug 24, 2010 at 6:26 AM, Martin Murphy > <[email protected]> wrote: >> Couchdb does not properly url decode usernames and passwords in the url. >> >> This prevents the majority of non ASCII characters from being used in either >> the username and password . This is a pretty high priority bug imo. >> >> It prevents couchapp for working on complex passwords and there are no >> alternatives using complex passwords for replication. >> >> It also prevents the very common scenario of using email addresses for >> logins/usernames. (If the logins are to be used with replication). >> >> Thanks for everything. Wish my erlang were better, I would fix this myself. >> > > Mmm it is the role oof the client to decode url/password from the url > and pass the right headers to servers. Which client are you using ? > > - benoit >
