couchdb-dev mailing list archives

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


Jan Lehnardt updated COUCHDB-466:

    Priority: Blocker  (was: Major)

I want to apply this before 0.10, but not tonight. Set to blocking.

> couchdb oauth doesn't work behind reverse proxy
> -----------------------------------------------
>                 Key: COUCHDB-466
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.10
>            Reporter: Benoit Chesneau
>            Priority: Blocker
>             Fix For: 0.10
>         Attachments: 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.

View raw message