Bug ID |
10906
|
Summary |
Empty values are missing in the output of urlencoded-form.value filter.
|
Product |
Wireshark
|
Version |
1.12.3
|
Hardware |
x86
|
OS |
Windows 8
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Version 1.12.3 (v1.12.3-0-gbb3e9a0 from master-1.12)
Copyright 1998-2015 Gerald Combs <[email protected]> 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 (32-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
with
MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Jan 7 2015), with
AirPcap.
Running on 32-bit Windows 8, build 9200, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz, with 2045MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Empty values are missing in the output of urlencoded-form.value filter.
For example, supposing there is an HTTP Post request with the following form
content: a=1&b=&c=3, (b doesn't has a value), if you use "tshark -Tfields
-eurlencoded-form.key -eurlencoded-form.value", you will get "a,b,c 1,3", thus
there are three keys but only two values, you can't determine b=3 or c=3.
A proper output of urlencoded-form.value filter should be "1,,3", which means
even if a form item has an empty value, you should not drop the value.
Would you please fix this? Thanks!
You are receiving this mail because:
- You are watching all bug changes.