Thanks for your quick and helpful feedback guys. I didn't realize the documentation was newer than the released binaries.
In the meanwhile I wrote a simple proxy handler in my .Net project to sidestep the cross domain issue for now. Looking forward to 1.3. thanks, Steve On Sat, Feb 16, 2013 at 9:43 AM, Алекс Zatvornitskiy < [email protected]> wrote: > By the way, you could do a development/prototyping with 1.3.x Couch DB > which you can makes from source. > > > On Sat, Feb 16, 2013 at 2:07 AM, Dave Cottlehuber <[email protected]> > wrote: > > > Hi Steve, > > > > The docs branch points to 1.3.x git repo, we don't have a docs 1.2.x > > branch unfortunately. Although Alex is working on this. Hopefully soon > > the distinction will be moot, when 1.3.0 rolls out the door. Sorry for > > the confusion in the meantime. I've made the wiki more obvious. > > > > A+ > > Dave > > > > On 15 February 2013 22:38, Steve Snively <[email protected]> wrote: > > > I just wanted to get clarification that CouchDB 1.2.1 does support CORS > > as > > > is stated here http://wiki.apache.org/couchdb/CORS and > > > > > > http://couchdb.readthedocs.org/en/latest/config_reference.html?highlight=cors > > > > > > I only ask because I have added the following sections to the local.ini > > > (x86 distribution), restarted, and still receive a "405 OPTIONS Method > > not > > > allowed" error in my XMLHttpRequest. > > > [httpd] > > > enable_cors=true > > > > > > [cors] > > > origins=* > > > > > > I'm running Chrome 26. The calling application is a PouchDB. > > > > > > If anyone has some insight I would love to hear it, as I'm currently a > > bit > > > puzzled whether it supports it or not. > > > > > > thanks, > > > Steve > > >
