Wireshark-bugs: [Wireshark-bugs] [Bug 5338] New: Improve the HTTP dissection of the Response Sta
Date: Mon, 25 Oct 2010 12:02:12 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5338

           Summary: Improve the HTTP dissection of the Response Status
                    Line
           Product: Wireshark
           Version: 1.4.1
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: robert@xxxxxxxxxxxxxx


Build Information:
Version 1.4.2-USBank (SVN Rev 34596 from /trunk-1.4)

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, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Oct
22 2010), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, 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.
--
There are two things that would improve the HTTP Response Status Line: 

1.) Conform to standard terminology. What Wireshark calls the Response Code is
more properly referred to as the Status Code.

2.) Make the Reason Phrase filterable/exportable. The Status Code portion of
the Response Status Line is currently filterable/exportable, but not the Reason
Phrase. This would be sufficient if only the standard Reason Phrases were used
because they could be inferred from the Status Code. But I have witnessed some
web server implementations that return non-standard text in the Reason Phrase
that includes diagnostic information specific to the request.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.