[ 
https://issues.apache.org/jira/browse/COUCHDB-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Lenz resolved COUCHDB-12.
-------------------------------------

    Resolution: Fixed

This has been fixed by merging the futon-async branch into trunk as of r648074.

> Using the @ symbol in the document ID causes strange results in CouchDB 
> browser (under the _utils path)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-12
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-12
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Administration Console
>            Reporter: Noah Slater
>            Assignee: Christopher Lenz
>            Priority: Minor
>
> What steps will reproduce the problem?
> 1. Within the CouchDB browser interface (_utils) create a document with an
> id of [EMAIL PROTECTED] - succeeds
> 2. Now try and do anything with that document through the browser
> interface:  The path changes to question marks - you cannot delete the
> document from the browser interface or add fields to the document
> 3.
> What is the expected output? What do you see instead?
> Does not appear to be a valid document.
> What version of the product are you using? On what operating system?
> Latest version 0.7xx from svn on Ubuntu
> Please provide any additional information below.
> --
> Comment 1 by [EMAIL PROTECTED], Nov 27, 2007
> This could be slightly related to the issue I just posted. I'd imagine 
> applying my
> patch would give him an error message about the revision not applying.
> It sounds like the same problem that occurs when you click the next and 
> previous
> links for a document. since the @ symbol is how you request revisions couchdb 
> will
> misinterpret the document request as a document revision request.
> --
> Comment 2 by [EMAIL PROTECTED], Nov 27, 2007
> here is a patch that at least returns an error message and redirects to the 
> database
> page again.
> It doesn't tackle the real problem which is that an @ symbol is allowed 
> unescaped in
> a docid.
> Apologies but it includes my previous patch for the doc revision requests 
> problem
> --
> Comment 4 by cmlenz, Feb 07, 2008
> Thanks for reporting this, I'll look into it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to