Wireshark-bugs: [Wireshark-bugs] [Bug 1958] HTTP parser limits with Content-Length
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1958
------- Comment #3 from drlisandroalvarez@xxxxxxxxxxx 2007-10-30 22:56 GMT -------
After some extra testing seems that what I've said in my previous note is not
totally true since there are some others values whose modulus is less than 2^31
and still the dissection doesn't work (at least automatically).
Guy, about point 2, I forgot to mention that I've used a HEAD request, so the
number of packets between the SYN and FIN TCP packets was very few. But as I've
said in the paragraph above, seems that the reason for not detecting the HTTP
response is not so much clear and needs more investigation. Anyway, perhaps all
this will get fixed by doing what you proposed in point 1.
The Content-Length has a "cosmetic" difference with the other headers, it lacks
of the trailing "\r\n".
The best solution which I don't know if it is doable on Wireshark would be to
just copy&paste the original string value as it is and doing the StrToInt for
internal proposes only. What do you think?
Cheers,
Loco
--
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.
