Wireshark-bugs: [Wireshark-bugs] [Bug 3785] New: Some HTTP responses don't decode with TCP reass
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3785
Summary: Some HTTP responses don't decode with TCP reassembly on
Product: Wireshark
Version: SVN
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: chcosta75@xxxxxxxxxxx
Chris Costa <chcosta75@xxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #3426| |review_for_checkin?
Flag| |
Created an attachment (id=3426)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3426)
HTTP Response Patch
Build Information:
TShark 1.3.0-CCOSTA
Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GLib 2.20.3, with WinPcap (version unknown), with libz 1.2.3,
without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8, with c-ares
1.6.0,
with Lua 5.1, without Python, with GnuTLS 2.8.1, with Gcrypt 1.4.4, with MIT
Kerberos, with GeoIP.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, GnuTLS 2.8.1,
Gcrypt 1.4.4.
Built using Microsoft Visual C++ 9.0 build 30729
--
The situation I encountered was with a response containing a content-type
header field, but no content-length. The reassembly seems to occur properly
but the reassembled PDU does not decode as HTTP.
I was able to correct this particular problem with the attached patch.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
