[
https://issues.apache.org/jira/browse/COUCHDB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damjan Georgievski updated COUCHDB-321:
---
Attachment: futon-proxy-fix.diff
attaching the fix.
ps. the nginx conf used for testing is:
server {
location / {
proxy_pass http://127.0.0.1:5984;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
}
location /db/ {
rewrite/db/(.*) /$1 break;
proxy_pass http://127.0.0.1:5984;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
}
> Futon breaks when used with a reverse proxy
> ---
>
> Key: COUCHDB-321
> URL: https://issues.apache.org/jira/browse/COUCHDB-321
> Project: CouchDB
> Issue Type: Bug
> Components: Futon
>Affects Versions: 0.9
> Environment: Affects all platforms.
>Reporter: Jack Moffitt
>Priority: Minor
> Attachments: futon-proxy-fix.diff, futon.patch
>
>
> It is often convenient to reverse proxy CouchDB at a url like /couch.
> Unfortunately, while CouchDB will work perfectly in this situation, Futon
> cannot handle it as jquery.couch.js uses absolute URLs to access all CouchDB
> functions.
> I've attached a small patch that fixes this problem by:
> 1. Adding a urlPrefix attribute to $.couch which it uses to construct its
> URLs.
> 2. Adding logic to the futon.js constructor that figures out a suitable
> prefix and sets $.couch.urlPrefix to use this.
> Any client code that makes use of $.couch will need to do something similar.
> Since only the application and the adminstrator will know what the prefix
> should be or how to deduce it, I didn't really know of a better way to handle
> this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
