http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2547
--- Comment #1 from Stephen Fisher <stephentfisher@xxxxxxxxx> 2008-05-15 14:14:21 PDT ---
Would it be possible for you to upgrade to a newer Wireshark/Tshark version to
see if this problem is still happening? We're now up to version 1.0. I tried
that command on one of my http pcap files and it works fine with the latest
version of Wireshark. There are two possibilities here: 1) There is a bug in
TShark in version 0.99.4 2) There is a bug in Tshark including 1.0 that is
triggered by something in your capture file. You're also welcome to attach the
capture file you're using to this bug and you can mark it as private so that
only the core developers can see it.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
