Wireshark · Wireshark-dev: Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?

Wireshark-dev: Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no

From: Guy Harris <guy@xxxxxxxxxxxx>

Date: Tue, 20 Jul 2010 02:44:50 -0700

On Jul 19, 2010, at 8:27 AM, Tarjei Knapstad wrote:

> After some more digging I found that the HTTP dissector does not
> search for and call subdissectors if there are no unprocessed bytes
> left in the packet. Does this mean that it's impossible to do any
> custom processing of HTTP GET requests in a subdissector,

Yes.

What sort of custom processing are you trying to do?

Follow-Ups:
- Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?
  - From: Tarjei Knapstad

References:
- [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?
  - From: Tarjei Knapstad
- Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?
  - From: Tarjei Knapstad

Prev by Date: Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?
Next by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 33587: /trunk/ /trunk/epan/dissectors/: packet-mac-lte.c /trunk/gtk/: compare_stat.c /trunk/: tap-comparestat.c
Previous by thread: Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?
Next by thread: Re: [Wireshark-dev] Correct way of adding a HTTP subdissector on port 80 with no content type?
Index(es):
- Date
- Thread