Hi Jan, You are welcome I updated the wiki to tell minimum configure options and minimum apache version
2009/1/21 Jan Lehnardt <[email protected]> > Hi Patrick, > > Thanks! I added the snippet to the wiki. If anyone > feels like adding some more explanation, that'd be > nice :) > > http://wiki.apache.org/couchdb/Apache_As_a_Reverse_Proxy#preview > > Cheers > Jan > -- > > On 21 Jan 2009, at 09:14, Patrick Antivackis wrote: > > Here is my config.All futon's tests are ok : >> >> <VirtualHost *:80> >> ServerAdmin [email protected] >> DocumentRoot "/opt/websites/web/www/dummy" >> ServerName couchdb.localhost >> AllowEncodedSlashes On >> ProxyRequests Off >> <Proxy *> >> Order deny,allow >> Deny from all >> Allow from 88.164.1.48 >> Allow from 127.0.0.1 >> </Proxy> >> ProxyPass / http://localhost:5984/ nocanon >> ProxyPassReverse / http://localhost:5984/ >> ErrorLog "logs/couchdb.localhost-error_log" >> CustomLog "logs/couchdb.localhost-access_log" common >> </VirtualHost> >> >> Hope it helps >> >> 2009/1/21 Jason Huggins <[email protected]> >> >> On Tue, Jan 20, 2009 at 6:31 PM, Glenn Rempe wrote: >>> >>>> Hi, >>>> >>>> I am experimenting with CouchDB and wanted to setup a virtual host and >>>> reverse proxy in my apache server that would expose couchdb to the net, >>>> >>> and >>> >>>> allow me to easily add apache basic auth on top (with the hope that some >>>> couchdb ruby clients support basic auth). >>>> >>>> However, when I set this up I discovered that many of the futon JS tests >>>> fail when run on the proxied url, but all pass when hitting the same >>>> >>> exact >>> >>>> couchdb install via a direct url. >>>> >>> >>> I had this problem, too. I had to add "AllowEncodedSlashes On" to my >>> virtual host config to get proxing working correctly. >>> >>> >>>> I did not see anything about this in the bug Jira. On initial >>>> >>> examination >>> >>>> this appears to be related to url escaping in the js tests. >>>> >>> >>> Yup. Sorry, though, for not documenting/blogging/sharing my fix before. >>> :-/ >>> >>> When I get the chance, I'll publish a slimmed downed and working >>> version of my vhost file that fixes this bug, but until then... try >>> added "AllowEncodedSlashes On" right inside your VirtualHost >>> declaration. >>> >>> cheers, >>> hugs >>> >>> >
