On Oct 20, 2014, at 6:43 AM, Michael Richardson <m...@sandelman.ca> wrote:
> print-x test case: > > 16c16 > < IP 127.0.0.1.55920 > 127.0.0.1.80: Flags [P.], seq 1:203, ack 1, win 8192, > options [nop,nop,TS val 1306300951 ecr 1306300950], length 202 > --- >> IP 127.0.0.1.55920 > 127.0.0.1.80: Flags [P.], seq 1:203, ack 1, win 8192, >> options [nop,nop,TS val 1306300951 ecr 1306300950], length 202: HTTP: GET / >> HTTP/1.1 > 38c38 > < IP 127.0.0.1.80 > 127.0.0.1.55920: Flags [P.], seq 1:5560, ack 203, win > 8192, options [nop,nop,TS val 1306300953 ecr 1306300951], length 5559 > --- >> IP 127.0.0.1.80 > 127.0.0.1.55920: Flags [P.], seq 1:5560, ack 203, win >> 8192, options [nop,nop,TS val 1306300953 ecr 1306300951], length 5559: HTTP: >> HTTP/1.1 200 OK > > Did something change with the print-http Yes, it now exists, whereas it didn't exist before. :-) I added a utility routine to print text protocols such as FTP, SMTP, HTTP, RTSP, SIP, etc., and added dissectors for FTP, SMTP, HTTP, and RTSP, and changed the SIP dissector to use those routines. Without -v, they just print the request/response line; with -v, they also print subsequent printable lines within the same TCP segment as the request/response line. _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
