[
https://issues.apache.org/jira/browse/COUCHDB-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gleave updated COUCHDB-1128:
-----------------------------------
Description:
According to the HTTP / 1.1 spec, the "identity" content-coding is to be used
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.
was:
According to the HTTP / 1.1 spec, the "identity" content-coding is to be used
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.
> 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
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> According to the HTTP / 1.1 spec, the "identity" content-coding is to be used
> 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
