Differences between revisions 4 and 5
Revision 4 as of 2004-10-30 15:28:49
Size: 908
Editor: OlivierBiot
Comment: First description of the HTTP preferences.
Revision 5 as of 2004-10-30 16:52:32
Size: 1367
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
When this preference is enabled, then the HTTP dissector will reassemble the HTTP header if it has been transmitted over more than one TCP segment. When this preference is enabled, then the HTTP dissector will reassemble the HTTP header if it has been transmitted over more than one TCP segment.  Although it is unusual for headers span multiple segments, it's not impossible, and this should be checked if you expect to view the contents of the HTTP conversation.
Line 8: Line 9:
When this preference is enabled, then the HTTP dissector will reassemble the HTTP body if it has been transmitted over more than one TCP segment. When this preference is enabled, then the HTTP dissector will reassemble the HTTP body if it has been transmitted over more than one TCP segment.  All but the smallest of responses will span multiple segments, so this preference should be checked if you expect to view the contents of the HTTP conversation.
Line 10: Line 12:
When this preference is enabled, any chunked coding will be reassembled if it was transmitted over more than one TCP segment. When this preference is enabled, any chunked transfer-coding response spanning multiple segments will be decoded and the payload (the body of the response) will be added to the protocol tree. This happens automatically for one segment responses.

Preferences/Protocols/HTTP

attachment:Preferences-Proto-HTTP.JPG

Reassemble HTTP headers spanning mutiple TCP segments

When this preference is enabled, then the HTTP dissector will reassemble the HTTP header if it has been transmitted over more than one TCP segment. Although it is unusual for headers span multiple segments, it's not impossible, and this should be checked if you expect to view the contents of the HTTP conversation.

Reassemble HTTP bodies spanning mutiple TCP segments

When this preference is enabled, then the HTTP dissector will reassemble the HTTP body if it has been transmitted over more than one TCP segment. All but the smallest of responses will span multiple segments, so this preference should be checked if you expect to view the contents of the HTTP conversation.

Reassemble chunked transfer-coded bodies

When this preference is enabled, any chunked transfer-coding response spanning multiple segments will be decoded and the payload (the body of the response) will be added to the protocol tree. This happens automatically for one segment responses.

Uncompress entity bodies

Enable this preference if gzip or deflate encoded (compressed) HTTP entities should be decoded. This allows the visualisation of the compressed data, and possibly the dissection of it.

HTTP_Preferences (last edited 2015-11-19 14:17:42 by PeterWu)