http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1966
ulf.lamping@xxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Comment #1 from ulf.lamping@xxxxxx 2007-10-31 19:14 GMT -------
Wireshark will only recognize most protocols right, if the start of the
conversation was captured - HTTP is no exception to this.
At first sight it seems that simply implementing "all on http port 80" must be
HTTP and therefore decoded like HTTP would be easy (well, beside that http is
used on other ports than 80) - but won't help a lot here. To properly decode
HTTP (and most other TCP based protocols), you'll need to find the start of the
HTTP messages. This could only be implemented trough heuristics ("sophisticated
guesswork") - but that will *often* fail.
All in all, it's not a bug or incomplete as it is today - it's very certain
that such an heuristic will cause more touble than it actually solves ...
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
