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 C742098B1 for ; Sun, 10 Mar 2013 19:01:14 +0000 (UTC) Received: (qmail 14389 invoked by uid 500); 10 Mar 2013 19:01:13 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 14296 invoked by uid 500); 10 Mar 2013 19:01:13 -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 13681 invoked by uid 99); 10 Mar 2013 19:01:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Mar 2013 19:01:13 +0000 Date: Sun, 10 Mar 2013 19:01:13 +0000 (UTC) From: "Volker Mische (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (COUCHDB-1689) CORS requests on attachments sometimes fail MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Volker Mische created COUCHDB-1689: -------------------------------------- Summary: CORS requests on attachments sometimes fail Key: COUCHDB-1689 URL: https://issues.apache.org/jira/browse/COUCHDB-1689 Project: CouchDB Issue Type: Bug Components: Database Core Reporter: Volker Mische In some cases CORS requests fail. I've identified two cases: 1. when using CORS and requesting attachments with doc?attachments=true the request failes 2. When an uncompressed attachments is requested directly with a range request The reason is that in those cases headers are encoded as binaries instead of lists. CORS is doing some string manipulations (string:to_lower/1) which fails when it gets binaries. Pull request with tests and fix is forthcoming. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira