This workaround seems to do the trick for the time being: if ($request_method = HEAD) { add_header Content-Length 0; add_header Content-Type text/plain; add_header Vary Accept-Encoding; return 200; } It might interfere with other HEAD requests, so I consider that as stopgap measureby stwissel - Nginx Mailing List - English
Hi Edho, I know -X HEAD is a hack, but it seems that is the way CouchDB might operate (haven't got a reply back from them). Worked before using an Apache HTTP reverse-proxy, but I like nginx much better. So what options do I have to make nginx behave the same for -X HEAD as it does for --head?by stwissel - Nginx Mailing List - English
I'm using nginx 1.7.7 as a reverse proxy in front of a Apache CouchDB. Access via browser to CouchDB data works like a charm. However I have trouble with replication (which runs via HTTPs). This is what I found out: CouchDB would issue a HTTP HEAD first and then perform GET/POST as per its algorythm. However the HEAD request times out. I then tried to replicate that behavior using CURL. This isby stwissel - Nginx Mailing List - English