This is our old Q&A Site. Please post any new questions and answers at

I am trying to analyze HTTP traffic where the HTTP body is zlib encoded. The packet details pane shows:

Hypertext Transfer Protocol
    POST /xxs/ HTTP/1.1\r\n
    Content-Type: text/xml; charset="utf-8"\r\n
    SOAPAction: \r\n
    Content-Encoding: zlib\r\n
    Text-Length: 550\r\n
    Content-Length: 312\r\n
    Connection: Close\r\n
    Content-encoded entity body (zlib): 312 bytes [Error: Decompression failed]
        Data (312 bytes)

So for some reason the decompression of the zlip compressed data is failing. When I export the raw bytes of the HTTP body to a file I can successfully decompress them with a command line tool (openssl zlib -d). That tells me the content is in fact validly zlib encoded.

What may be causing the zlib decompression to fail in Wireshark? Is there anything further I could try to do to get this to work?

The problem occurs both in

  • the current version 1.8.5 (SVN Rev 47350 from /trunk-1.8) on Windows 7 (zlib1.dll is present in Wireshark folder)
  • Version 1.2.15 on CentOS (the only version I was able to get hold of on Linux right now)

asked 20 Feb '13, 09:57

tobias's gravatar image

accept rate: 0%

edited 20 Feb '13, 10:00

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 20 Feb '13, 09:57

question was seen: 2,539 times

last updated: 20 Feb '13, 10:00

p​o​w​e​r​e​d by O​S​Q​A