couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments
Date Tue, 19 Apr 2011 20:41:06 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Filipe Manana resolved COUCHDB-1128.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1
                   1.0.3

Patch, with tests, applied to 1.0.x, 1.1.x and trunk.


> Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed
attachments
> ----------------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-1128
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1128
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.0.2
>         Environment: CouchOne
>            Reporter: Andrew Gleave
>            Priority: Minor
>              Labels: http
>             Fix For: 1.0.3, 1.1
>
>         Attachments: COUCHDB-1128.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> According to the HTTP / 1.1 spec, the "identity" content-coding is to be used only in
the Accept- Encoding header, and should not be used in the Content-Encoding header. Currently,
any uncompressed attachment which is retrieved from CouchDB will have Content-Encoding:identity
specified in its response header.
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.5
> All browsers and most proxies seem to ignore the header and function correctly. However,
Microsoft's ISA 2006 proxy seems to reject the entire request, meaning all attachments are
inaccessible from behind the proxy.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message