https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5182
Summary: Wireshark doesn't ignore HTTP's Content-Length when
Transfer-Encoding is sent
Product: Wireshark
Version: 1.5.x (Experimental)
Platform: x86-64
OS/Version: Windows 7
Status: NEW
Severity: Minor
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: boaz.brickner@xxxxxxxxx
Created an attachment (id=5123)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5123)
Example packets pcap file with the descripted problem
Build Information:
Version 1.5.0-SVN-34063 (SVN Rev 34063 from /trunk)
Copyright 1998-2010 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 GTK+ 2.16.6, (64-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep
5 2010), with AirPcap.
Running on 64-bit Windows 7, build 7600, with WinPcap version 4.1.2 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
While testing Pcap.Net (http://pcapdot.net), I've found this bug in Wireshark:
In RFC 2616 (HTTP) it is specifically written:
If a message is received with both a
Transfer-Encoding header field and a Content-Length header field,
the latter MUST be ignored.
However, when Wireshark parses an HTTP packet that contains both fields, it
uses the Content-Length field. When these fields don't match it causes a
problem parsing the packet.
In the attached pcap file, there are two HTTP packets.
Both have a chunked Transfer-Encoding with a valid chunked body.
The first has a valid Content-Length field and is parsed fine.
The second has an invalid Content-Length field (shorter than what should be)
and isn't parsed well.
Thank you,
Boaz.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.