XML-RPC
  1. XML-RPC
  2. XMLRPC-153

content-length header incorrect when using gzip

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0, 3.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      UNIX (FC3), Sun JDK1.5.0_10

      Description

      When doing some testing using the ws-xmlrpc client libraries I ran across a bug in its calculation of the content-length HTTP header when using gzip compression but not HTTP chunked transfer. The client incorrectly sets the content-length to the length of the uncompressed data, rather than the compressed data it sends. This happens using both 3.0 and 3.1 client libraries.

      I see some activity on ws-xmlrpc-dev from September 2007 but no mention of any resolution. I did a quick bug search and found nothing - my apologies if this is already being tracked somewhere else and I missed it.

      From the mail thread, a link to the relevant part of the HTTP spec:

      http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.13

      1. patch.txt
        3 kB
        Balázs Póka

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Andy Meyer
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development