Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 4708 invoked from network); 24 Aug 2010 04:26:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 Aug 2010 04:26:51 -0000 Received: (qmail 13607 invoked by uid 500); 24 Aug 2010 04:26:50 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 13315 invoked by uid 500); 24 Aug 2010 04:26:48 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 13307 invoked by uid 99); 24 Aug 2010 04:26:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Aug 2010 04:26:47 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Aug 2010 04:26:40 +0000 Received: by fxm10 with SMTP id 10so4371490fxm.11 for ; Mon, 23 Aug 2010 21:26:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.132.132 with SMTP id 4mr292865hbr.47.1282623978977; Mon, 23 Aug 2010 21:26:18 -0700 (PDT) Received: by 10.239.136.9 with HTTP; Mon, 23 Aug 2010 21:26:18 -0700 (PDT) Date: Mon, 23 Aug 2010 23:26:18 -0500 Message-ID: Subject: Bug in Password From: Martin Murphy To: dev@couchdb.apache.org Content-Type: multipart/alternative; boundary=001485f1ec1ea5b87d048e8a2ac3 --001485f1ec1ea5b87d048e8a2ac3 Content-Type: text/plain; charset=ISO-8859-1 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. --001485f1ec1ea5b87d048e8a2ac3--