[
https://issues.apache.org/jira/browse/COUCHDB-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166972#comment-13166972
]
Filipe Manana commented on COUCHDB-1320:
----------------------------------------
"> Why x-couchdb-vhost-path couldn't have been used for the oauth calculation ?"
Not understanding your question. The changes I made to couch_httpd_oauth.erl
make use of the header x-couchdb-vhost-path to compute the OAuth signature.
"nm . I am just confused by the the user_ctx thing I think. Sound
really overkill."
Overkill in which sense?
What's important is passing a user_ctx to the 2nd (post rewrite resolution)
couch_httpd:handle_request_int call, so that it doesn't run all the auth
handlers again. About using the process dictionary versus a new
couch_httpd:handle_request_int function with an extra argument (UserCtx), I
don't see any of them overkill compared to the other.
> 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
