Indeed in some cases, simple space or '-' works in attachment name, but '+'
attachement with ou without buffering. I also noticed some URI escape
use (browser, Android, iOS, .NET etc). As long as CouchDB can have ' + ' in
it...
Post by Jan LehnardtHi Max,
I use couch (2.1) in a sub dir via nginx as a proxy with the suggested
conf you mentioned in your first email. The only difference is that I turn
off buffering at the same level instead of filtering for â_changesâ (I may
change that). I have attachments with â-â , â_â and â â just not with â+â.
I tried adding a doc with a â+â and uploaded it via Fauxton. The â+â in
the name is converted to a space (â â) in the attachment listing of the
respective couch doc. If I try to retrieve the attachment directly, I can
either use a â%20â where the space is or also â+â. So it seems that the â+â
is reserved as a substitute for a space character and works but maybe not
as expected. The other chars should work as expected.
location /couchdb {
rewrite /couchdb/(.*) /$1 break;
proxy_pass http://localhost:5984;
proxy_redirect off;
proxy_buffering off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
Renato
Post by maxThanks for your answers.
@Jan
I already tried this and it cannot be used since the sub directory part
remains in the URI. To be able to use it without the trailing '/' I would
need to tell CouchDB to listen on "127.0.0.1:5984/couchdb" and (I
think) I
Post by maxcannot.
You are right "this is more an nginx than a CouchDB question" but CouchDB
2.0 doc contains this "Reverse proxy for a sub directory" part that seems
not correct, that's why I was hopping help from CouchDB users :).
@Sinan
You are completely right but only with '/' and actually this was exactly
my
Post by maxconfiguration when I did not need sub directories but now I do.
Post by Jan LehnardtHi Max,
Sorry for not being able to answer your actual question, I still want to
draw your attention to the need for further nginx location needs (i.e.
_changes): Here's an example of a working configuration when listening
at
Post by maxPost by Jan Lehnardtthe root / and using ssl.
location ~ ^/(.*)/_changes {
proxy_pass http://couchdb_node;
proxy_redirect off;
proxy_buffering off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Ssl on;
}
location / {
proxy_pass http://couchdb_node;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Ssl on;
}
Post by Jan LehnardtHi Max,
this is more an nginx than a CouchDB question, but
https://serverfault.com/questions/459369/disabling-
url-decoding-in-nginx-proxy#463932 suggests that if you use proxy_pass
without a uri (not even a slash), that things should work.
Can you verify youâre using `proxy_pass http://localhost:5984;` and
not
Post by maxPost by Jan LehnardtPost by Jan Lehnardte.g. `proxy_pass http://localhost:5984/;`. If you are, you should
open a
Post by maxPost by Jan LehnardtPost by Jan Lehnardtticket with the nginx team.
Best
Jan
--
Post by maxHi,
To make CouchDB listen as sub directory, doc says (
https://cwiki.apache.org/confluence/display/COUCHDB/Nginx+as+a+proxy)
to
Post by Jan LehnardtPost by maxlocation /couchdb {
rewrite /couchdb/(.*) /$1 break;
proxy_pass http://localhost:5984;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
But this cannot be used for attachment with special character such as
+,
Post by Jan LehnardtPost by max-, ,
For those CouchDB will send back: "{"error":"not_found","reason"
:"Document
Post by maxis missing attachment"}"
location /couchdb/ {
rewrite ^ $request_uri;
rewrite ^/ couchdb /(.*) $1 break;
return 400;
proxy_pass http://127.0.0.1:5984/$uri;
}
But doing so I cannot access CouchDB root (http://127.0.0.1/couchdb)
since
Post by maxit will result in Nginx 500 error (zero length URI).
Do you know a better Nginx configuration?
Thanks,
Max
--
https://neighbourhood.ie/couchdb-support/