Here's the commit:

http://svn.apache.org/viewvc?view=revision&revision=1064421

On Fri, Jan 28, 2011 at 11:42 AM, Sebastian Cohnen
<[email protected]> wrote:
> I only saw one of your commits (rev 1064417) to trunk. But maybe I'm wrong.
>
> On 28.01.2011, at 16:41, Paul Davis wrote:
>
>> I thought I backported it already.
>>
>> On Fri, Jan 28, 2011 at 1:52 AM, Sebastian Cohnen
>> <[email protected]> wrote:
>>> if this is a blocker, shouldn't this be fixed for 1.0.x as well?
>>>
>>> best,
>>> sebastian
>>>
>>>
>>> Am 28.01.2011 um 02:50 schrieb "Paul Joseph Davis (JIRA)" <[email protected]>:
>>>
>>>>
>>>>     [ 
>>>> https://issues.apache.org/jira/browse/COUCHDB-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>>>  ]
>>>>
>>>> Paul Joseph Davis resolved COUCHDB-1039.
>>>> ----------------------------------------
>>>>
>>>>       Resolution: Fixed
>>>>    Fix Version/s:     (was: 1.1)
>>>>                   1.2
>>>>
>>>> Applied in 1064417
>>>>
>>>>> "High ASCII" characters on PUT'ed URL causes db to misbehave
>>>>> ------------------------------------------------------------
>>>>>
>>>>>                Key: COUCHDB-1039
>>>>>                URL: https://issues.apache.org/jira/browse/COUCHDB-1039
>>>>>            Project: CouchDB
>>>>>         Issue Type: Bug
>>>>>   Affects Versions: 1.0.1, 1.2
>>>>>           Reporter: Thiago Arrais
>>>>>           Priority: Blocker
>>>>>            Fix For: 1.2
>>>>>
>>>>>        Attachments: badtext.tar.gz, validate_utf8_docid.patch
>>>>>
>>>>>
>>>>> I've tried to PUT a doc to an id containing "high ascii" characters and 
>>>>> couchdb (correctly, I imagine) refuses to save it and responds with an 
>>>>> error. But any subsequent queries to the db special _all_docs document 
>>>>> returns a double response (200 and 500) (much like COUCHDB-48) with a 
>>>>> bad_utf8_character_code error.
>>>>> Tested on both 1.0.1 (from the Ubuntu Maverick repos) and svn 
>>>>> (1.2.0a106148)
>>>>
>>>> --
>>>> 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