[ 
https://issues.apache.org/jira/browse/COUCHDB-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166968#comment-13166968
 ] 

Benoit Chesneau commented on COUCHDB-1320:
------------------------------------------

I don't remember to have time to review it though .... I like email
bump sometimes.

Also I don't see why a registry process is used here? What is the reason?
Why x-couchdb-vhost-path couldn't have been used for the oauth calculation ?


- benoƮt


On Sat, Dec 10, 2011 at 9:05 PM, Filipe Manana (Resolved) (JIRA)

                
> OAuth authentication doesn't work with VHost entry
> --------------------------------------------------
>
>                 Key: COUCHDB-1320
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1320
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.1
>         Environment: Ubuntu
>            Reporter: Martin Higham
>            Assignee: Filipe Manana
>             Fix For: 1.2
>
>         Attachments: Fix-OAuth-that-broke-with-vhost.patch, 
> fdmanana-0001-Fix-OAuth-authentication-with-VHosts-URL-rewriting.patch
>
>
> If you have a vhost entry that modifies the path (such as my host.com = 
> /mainDB/_design/main/_rewrite ) trying to authenticate a request to this host 
> using OAuth fails.
> couch_httpd_oauth uses the modified path rather than the original 
> x-couchdb-vhost-path when calculating the signature.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to