Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2004-10-29 19:28:21
Size: 89
Editor: StephenFlynn
Comment: Initial Creation of page
Revision 11 as of 2007-01-22 10:35:42
Size: 1509
Editor: apache
Comment: added wireshark (not ethereal) screen-shot
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
== Preferences/Protocols/HTTP == = Preferences/Protocols/HTTP =
attachment:Preferences-Proto-HTTP.JPG
attachment:http-prefs.png
Line 4: Line 6:
=== Reassemble HTTP headers spanning multiple TCP segments: ===
Line 5: Line 8:
=== Enable MAC name resolution === 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 multiple 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.[[BR]]
See ["TCP Reassembly"] for an example on how to use this to extract JPEG images from a capture.

=== 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.

Preferences/Protocols/HTTP

attachment:Preferences-Proto-HTTP.JPG attachment:http-prefs.png

Reassemble HTTP headers spanning multiple 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 multiple 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.BR See ["TCP Reassembly"] for an example on how to use this to extract JPEG images from a capture.

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)