couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COUCHDB-466) couchdb oauth doesn't work behind reverse proxy
Date Tue, 18 Aug 2009 17:12:14 GMT

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

Jan Lehnardt closed COUCHDB-466.
--------------------------------

    Resolution: Fixed

fixed the tests:
 - wrapped config changes in run_on_modified_server
 - wrap lines at 80 chars
 - use TEquals() instead of T()

Applied in r805500.

> couchdb oauth doesn't work behind reverse proxy
> -----------------------------------------------
>
>                 Key: COUCHDB-466
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-466
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.10
>            Reporter: Benoit Chesneau
>            Priority: Blocker
>             Fix For: 0.10
>
>         Attachments: forwarded_for2.patch, x_forwarded_host.diff
>
>
> Currently oauth doesn't work behind a reverse proxy because signature is based on Host.
Reverse proxy like apache, lighttpd pass to the proxied server some header that help him to
know which host is forwared. Apache send X-Forwarded-For, Lighttpd X-Host, ....
> Patch attached fix this issue by testing if a custom forwarded host header is present
and use it as Host. If it isn't present it will use Host header of fallback on socket detection
like it is currently. All tests pass.

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


Mime
View raw message