https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5718
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jeff.morriss.ws@xxxxxxxxx
Resolution| |DUPLICATE
--- Comment #7 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-03-24 19:17:31 PDT ---
(In reply to comment #5)
> (In reply to comment #4)
> > Well, this is wonderfully annoying.
> >
> > I think I have some traces where HTTP traffic to and from port 631 is IPP
> > traffic but does *NOT* have a Content-Type of application/ipp.
> >
> > This is a trace where some HTTP traffic to and from port 631 is IPP traffic,
> > with a Content-Type of application/ipp, and other traffic isn't.
> >
>
> I noticed the same thing as I looked at various other Wireshark IPP captures.
>
> I started to wonder if the right solution might be to register port 631 (IPP)
> only for HTTP and let the Content-Type determine the sub-dissector called
> (including IPP).
Yep, that's what's currently done, in fact. I think most if not all of that
happened under bug 6765.
*** This bug has been marked as a duplicate of bug 6765 ***
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
