http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1958
guy@xxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|Windows XP |All
Platform|PC |All
------- Comment #2 from guy@xxxxxxxxxxxx 2007-10-30 21:49 GMT -------
The only machine I use on a regular basis that could even hope to support doing
a verbose dissection of that entire message is my MacBook Pro, which has a Core
2 Duo and hence a 64-bit processor, and even then I'd have to upgrade to
Leopard to support a 64-bit version of Wireshark. :-)
There are two issues here:
1) In order to do any reassembly of HTTP payloads at all, we have to
convert the content length to an integer, and currently we convert it to a
32-bit integer and display that integer. We should probably make it a 64-bit
integer.
2) We should probably have some way to limit the amount of reassembly we do
*AND* at least partially do the rest of the reassembly, even if we keep only
the first N bytes (for some reasonable value of N so that most reassemblies
succeed in their entirety) of the reassembled data, so we still do the best we
can at showing the reassembled packet.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
