Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of a.zatvornitskiy@gmail.com
 designates 209.85.215.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL+Y1ns8hhX70jWbxggoacbfY+HP438Fko0xcux4==P6ObnPyw@mail.gmail.com>
References: 
 <CAJvwepbDJFwZ9ncFg4kGE4bJDS6X4O0VaSFDGDfN_2FOkXe44Q@mail.gmail.com>
	<CAL+Y1ns8hhX70jWbxggoacbfY+HP438Fko0xcux4==P6ObnPyw@mail.gmail.com>
Date: Sat, 16 Feb 2013 17:43:47 +0200
Message-ID: 
 <CAKGaSrTXY8tbWUKfy3UVMrhXdtkscb62ZJjsspb+yCEoCVrEhQ@mail.gmail.com>
Subject: Re: Clarifying CouchDB CORS support
From: =?UTF-8?B?0JDQu9C10LrRgSBaYXR2b3JuaXRza2l5?= <a.zatvornitskiy@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=e0cb4efe30c88ef46804d5d95b14

--e0cb4efe30c88ef46804d5d95b14
Content-Type: text/plain; charset=ISO-8859-1

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 <dch@jsonified.com> 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 <stevesnively@gmail.com> 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
>

--e0cb4efe30c88ef46804d5d95b14--