On 4 mei 2011, at 23:33, Jeff Morriss wrote:
> Sake Blok wrote:
>> On 4 mei 2011, at 22:48, Jeff Morriss wrote:
>>> Sake Blok wrote:
>>>> One case that can cause a problem is when the first segment of a PDU is received out-of-order. Or did your recent work also handle this exception, Jeff?
>>> Yep, that's the case rev 36304 fixed.
>> Unfortunately not, I just constructed a file in which the first segment of the HTTP-response PDU comes after the second segment of that PDU. And dissection still fails as there is not yet a segment in tcpd->fwd->multisegment_pdus for that seq.
>
> Doh! You're right. In fact what I fixed was when you actually *see* the first packet more than once.
I remembered a bug report on this (but could not find it earlier tonight): https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4727
And here is my fabricated file as well...
Sake
Attachment:
first-segment-ooo.cap
Description: Binary data