I have the following HTTP frame: POST /Usage/Upload?compression=gzip HTTP/1.1 How can I show it decompressed? Please note: It is a POST (to the server) not a GET (from the server) asked 02 Jul '13, 10:46 Hanky |
One Answer:
sounds like your application is doing the compression, so it's (most certainly) not the built in compression available in HTTP. As I don't have a sample capture file, I would say, that it's only possible to show the POST payload uncompressed
BTW: If you are able to provide a sample capture file (google docs, dropbox, etc.) we might be able to give more information/details. Regards answered 02 Jul '13, 11:11 Kurt Knochner ♦ |
POST /Usage/Upload?compression=gzip HTTP/1.1
Host: services.robotstudio.com
Content-Length: 1388
Expect: 100-continue
Connection: Keep-Alive
HTTP/1.1 100 Continue
H4sIAAAAAAAEAOy9B2AcSZYlJi9tynt/SvVK1+B0oQiAYBMk2JBAEOzBiM3mkuwdaUcjKasqgcplVmVdZhZAzO2dvPfee++999577733ujudTif33/8/XGZkAWz2zkrayZ4hgKrIHz9+fB8/Iv7Hv/cffFVNqvZ1u54V1VdNdpH/zE/u/sbJNj3fPj1+evoqfXL6+dkL/P0bJ6/zpimq5dnss/Pz3XzvfO98+/4s393ef7CTbx/sne9v39vNHh5k9x7s39slKF9k03mxzNF+crCT55OH2/f3HlD73f2d7cn93U+3s8n+7GC6f29n9nDfwn/dZnX72c6Duzt7d/d2du+luzuP9nYf7d0PW3zVTv1GOwem0Zevz2b5si3Oi7z+7ItiWldNdd6m3y2Ws+qqSV+8ST8d744ffLqzm77O68timqcvs+nbdBev/mReo4fPTJPxp/fv3/sU3zzPlhdrItBn+XL7q9c/c7q8KItmnm59tSzafJYSTm3e3EHLJ0W7JEQ/u7f3Gycnz18ZkPvjnfG9nXu7D8fU0/NqmpU3wjperczb98e798f7Dx/ujfc+pfefrIty9ia7+OxlXc3W05aacPOTarHIlrPnRPfPPjp59PvS1xd1tkifFWXe/L7HT56kZ8vZumnrIivTsze/L09/MW3s78IKKbr7fZ8US//Dcf4u/yjlbvwh0p+3pQ1hM6XXqvqkqvOTar1sP9v1Pn1eXRREFvfF/LrBB1/ki6q+/mx358G9vZ2H9/aJVz4/f3eS1bMX2SJvPvvJL66yOk9f/+Tnx+m9p/zl07q4zOun6Pcz4o+93Z2de94XStXmswfj3X2aampA/b1YL54WzarMrhvBq1hk9bV+9CpvqnINQn+2u3ew8+5gZ+c3Tl7ly1leE589Lep82qLzp9UiK5afPS4xw0c009nyi+OTz3Z2tndOtvcebt+7v/303vZ9YtTv0js0Kw2+frxevl1WV0t6gaZwtW7z+otsuT7Ppu0a8GWII5q96dhrUs3y0gz/ J4u6XdOsviyz9ryqFzSAk9fXTZsv3lyv8s8I2+fE68uGKGJ/fZZngO998jy/JJDP6jwHAfJFsV7oNwzlxTHJdbEkwpRny6bNSmqblQ01fkIyRB9c5CydL8EN9qM32eRFfgW8y6p+M88X9F25zgNFc/riqagZ/Pv8y899zbOz84j+t38wPiDKH9w/+JnTd/mU5mJ5ofz+M+Dv03dF+zPHJAuXNO0z/639e5+6t/JZ9yXXZ4DE6zfHb177aLypaMBvCsLegX6wf0Cg9TvLyV4j0iFg2d094tqXefb2u1X9lhB/nbefPTy4v7Pz6c6BfKHz97r4Qf7ZPfr03r0dvOMwscj9PwEAAP//WtE9aLcFAAA= HTTP/1.1 200 OK
Cache-Control: private
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Tue, 02 Jul 2013 08:34:40 GMT
Content-Length: 0
that's not only compressed but also MIME encoded.
You can decode it on Linux with this command:
Result (part of it):
As @Kurt suspected, the compression is done at the (web)application layer, not at the HTTP layer. This means wireshark has no knowledge on how to interpret the data and is therefor not able to decompress it for you.