Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Clarifying CouchDB CORS support
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: 
 <CAJvwepbDJFwZ9ncFg4kGE4bJDS6X4O0VaSFDGDfN_2FOkXe44Q@mail.gmail.com>
Date: Fri, 15 Feb 2013 22:47:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FC0BD41-3915-48DD-9B29-B453D576E0F3@apache.org>
References: 
 <CAJvwepbDJFwZ9ncFg4kGE4bJDS6X4O0VaSFDGDfN_2FOkXe44Q@mail.gmail.com>
To: user@couchdb.apache.org


On Feb 15, 2013, at 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

First sentence:

> WARNING!! This page is a temporary gathering spot for CORS =
documentation while the git branch is in development.

It will ship as EXPERIMENTAL in 1.3.0

Cheers
Jan
--=20


> and
> =
http://couchdb.readthedocs.org/en/latest/config_reference.html?highlight=3D=
cors

>=20
> 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=3Dtrue
>=20
> [cors]
> origins=3D*
>=20
> I'm running Chrome 26.  The calling application is a PouchDB.
>=20
> If anyone has some insight I would love to hear it, as I'm currently a =
bit
> puzzled whether it supports it or not.
>=20
> thanks,
> Steve