CouchDB
  1. CouchDB
  2. COUCHDB-1128

Erroneous "identity" Content-Coding supplied to Content-Encoding header for uncompressed attachments

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0.2
    • Fix Version/s: 1.0.3, 1.1
    • Component/s: HTTP Interface
    • Labels:
    • Environment:

      CouchOne

    • Skill Level:
      Regular Contributors Level (Easy to Medium)

      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.

      1. COUCHDB-1128.patch
        0.6 kB
        Paul Joseph Davis

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        1d 3h 36m 1 Filipe Manana 19/Apr/11 21:40
        Filipe Manana made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.0.3 [ 12316107 ]
        Fix Version/s 1.1 [ 12314933 ]
        Resolution Fixed [ 1 ]
        Hide
        Filipe Manana added a comment -

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

        Show
        Filipe Manana added a comment - Patch, with tests, applied to 1.0.x, 1.1.x and trunk.
        Hide
        Paul Joseph Davis added a comment -

        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.

        Show
        Paul Joseph Davis added a comment - 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.
        Paul Joseph Davis made changes -
        Attachment COUCHDB-1128.patch [ 12476636 ]
        Hide
        Filipe Manana added a comment -

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

        Show
        Filipe Manana added a comment - Good catch. Want to provide a patch? Should be very very simple to do it.
        Andrew Gleave made changes -
        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.
        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.
        Andrew Gleave made changes -
        Field Original Value New Value
        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.
        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.
        Andrew Gleave created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Andrew Gleave
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 0.5h
              0.5h
              Remaining:
              Remaining Estimate - 0.5h
              0.5h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development