| -----Original Message-----
| From: Anders Broman (TN/EAB)
|
| Hi,
| I have no knowledge about the http protocol so I can't say
| anything about the similarities,
| but in general it should be advantageous to make common
| code/routines for all types of text based
| protocolls ( HTTP,SIP,MEGACO,MGCP,RTSP..comes to mind )as it
| looks to be the same type of problem to parse them.
That's the reason why we should add a tvb_get_rfc2822_header_field(). All
those text-based protocols refer to RFC822 or RFC2822 (which obsoleted
RFC822). Note that RFC[2]822 implies 7-bit US-ASCII characters; look at MIME
specs for non-ASCII extension. Anyway, all headers share a common syntax:
header-name ":" header-value CRLF
where space and tabs may appear before and/or after the colon, and CRLF
sometimes does not contain the LF.
| And the solutions looks different in each dissector.
This is the difference between parsing data and interpreting it :)
| -----Original Message-----
| From: Guy Harris
|
| Should the SIP and HTTP dissector share code to parse headers? We
| should perhaps make common code to handle the headers, with whatever
| features are needed for both protocols.
