Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-Id: <DA43AEE6-9AB5-4CBB-950D-53DF929D32E0@bitextender.com>
From: =?ISO-8859-1?Q?David_Z=FClke?= <david.zuelke@bitextender.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: ID encoding inconsistencies
Date: Wed, 24 Jun 2009 13:06:34 +0200

Ohai,

whilst playing around with some url encoding edge cases (for http://www.phpcouch.org/) 
, I came across the following two issues:

a) for a document "foo" with attachment "bar/baz", both "foo/bar/baz"  
and "foo/bar%2Fbaz" work. I believe that only the latter should be  
possible as that would be consistent with other IDs (design documents,  
view names and document IDs)
b) if a design document contains a view with a slash, then calling "/ 
testdb/_design/lolcats/_view/all%2Fyour%2Fbase" works, while "/testdb/ 
_design/lolcats/_view/all/your/base" gives an HTTP 405 Method Not  
Allowed response instead of a 404 which I think would be correct and/ 
or consistent with the other cases where IDs are not found, right? It  
should act like when calling a non-existant view I think.

Should I open tickets for these two, or am I just overlooking  
something obvious?

Cheers,

- David