Empty Content-Encoding in SOAP requests when using gzip Accept-Encoding in request

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 3.13.2
    • Affects Version/s: 3.13
    • Component/s: None
    • 3.13

      If you:

      • Enable gzip compression in JIRA under General Configuration
      • Send a SOAP request that accepts a compressed response

      With the Accept-Encoding header:

      $ wget -O - -S --header 'Accept-Encoding: gzip' http://localhost:8080/rpc/soap/jirasoapservice-v2?wsdl  > /dev/null

  HTTP/1.1 200 OK
  Server: Apache-Coyote/1.1
  Content-Encoding:
  Vary:
  Content-Type: text/xml;charset=utf-8
  Date: Tue, 23 Sep 2008 02:27:31 GMT
  Connection: close

      Without the Accept-Encoding header:

      $ wget -O - -S http://localhost:8080/rpc/soap/jirasoapservice-v2?wsdl  > /dev/null

  HTTP/1.1 200 OK
  Server: Apache-Coyote/1.1
  Content-Type: text/xml;charset=utf-8
  Date: Tue, 23 Sep 2008 02:31:45 GMT
  Connection: close

      The problem is that some clients break while parsing the empty Content-Encoding, and such a header does not seem correct. Can please someone take a look at it, and report their findings?

            Assignee:
            Scott Farquhar
            Reporter:
            Diego Alonso [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: