Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Sat, 15 Oct 2011 14:53:11 +0000 (UTC)
From: "Mounir Lamouri (Created) (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1591954470.17322.1318690391865.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (COUCHDB-1308) CouchDB isn't compatible with CORS
 editor draft
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

CouchDB isn't compatible with CORS editor draft
-----------------------------------------------

                 Key: COUCHDB-1308
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1308
             Project: CouchDB
          Issue Type: Bug
          Components: HTTP Interface
    Affects Versions: 1.1, 1.0.2
            Reporter: Mounir Lamouri
            Priority: Blocker


CORS editor draft [1] requests that for non-simple HTTP requests (like PUT or DELETE methods), the OPTIONS method should be used to know if those methods are allowed by the server [2]. If the server returns a status code different than 200, the User Agent should consider the request as not allowed thus shouldn't do the original request (with PUT or DELETE methods).

Gecko/Firefox is following this draft which makes CouchDB not accessible cross-domain with Firefox and all Gecko-based browsers. In addition, given that this is a behavior requested per specs, CouchDB will not work cross-domain with all future User Agent following it.

Tested with 1.0.2 and 1.1.0

[1] http://dvcs.w3.org/hg/cors/raw-file/tip/Overview.html
[2] See 7.1.5 "Cross-Origin Request with Preflight", 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira