Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CE1F817DB5 for ; Mon, 10 Nov 2014 19:25:30 +0000 (UTC) Received: (qmail 62963 invoked by uid 500); 10 Nov 2014 19:25:30 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 62905 invoked by uid 500); 10 Nov 2014 19:25:30 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 62894 invoked by uid 99); 10 Nov 2014 19:25:30 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2014 19:25:30 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id BAC009A41E4; Mon, 10 Nov 2014 19:25:29 +0000 (UTC) From: chewbranca To: dev@couchdb.apache.org Reply-To: dev@couchdb.apache.org References: In-Reply-To: Subject: [GitHub] couchdb-chttpd pull request: 2080 port cors Content-Type: text/plain Message-Id: <20141110192529.BAC009A41E4@tyr.zones.apache.org> Date: Mon, 10 Nov 2014 19:25:29 +0000 (UTC) Github user chewbranca commented on the pull request: https://github.com/apache/couchdb-chttpd/pull/8#issuecomment-62439223 @kxepal this is a refactor of the `couch_httpd_cors` implementation and was based on it. I think this is a cleaner implementation that is more easily tested, but as with the rest of `chttpd` it doesn't support vhosts yet, so I don't think we should completely replace `couch_httpd_cors` right now. We still need to consolidate down to one http layer and I think that would be the best time to remove the duplication. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---