You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Andrew Gleave (JIRA)" <ji...@apache.org> on 2011/04/18 19:06:05 UTC

[jira] [Created] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

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


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

[jira] [Commented] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/COUCHDB-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021114#comment-13021114 ] 

Filipe Manana commented on COUCHDB-1128:
----------------------------------------

Good catch.
Want to provide a patch? Should be very very simple to do it.

> 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 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

[jira] [Commented] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/COUCHDB-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021146#comment-13021146 ] 

Paul Joseph Davis commented on COUCHDB-1128:
--------------------------------------------

The attached patch should fix it. If someone wants to write a test and run the test suite and all that jazz let me know.

> 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
>         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

[jira] [Resolved] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
     [ 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

[jira] [Updated] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

Posted by "Andrew Gleave (JIRA)" <ji...@apache.org>.
     [ 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 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 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

[jira] [Updated] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

Posted by "Andrew Gleave (JIRA)" <ji...@apache.org>.
     [ 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

[jira] [Updated] (COUCHDB-1128) Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis updated COUCHDB-1128:
---------------------------------------

    Attachment: COUCHDB-1128.patch

> 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
>         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