> From: André Warnier [mailto:a...@ice-sa.com] > I think I'll have to refresh my TCP knowledge base, to see if there is > any byte somewhere in a TCP header specifying the internet protocol. > But I don't think so.
Sort of :-). The nearest you get is the four bytes specifying the source and destination port numbers - though as you already know that's subject to considerable latitude in interpretation! In particular, if one of those values is a well-known port (http://www.iana.org/assignments/port-numbers), the corresponding protocol RFC-SHOULD* be in use.... - Peter * Acronym decoder for those who are about to complain: Internet Engineering Task Force (IETF) Requests for Comments (RFCs) frequently make use of MUST, SHOULD, MAY, SHOULD NOT or MUST NOT (capitalised in that way) to indicate how a "correct" system behaves. This has entered some more general Internet parlance, so RFC-SHOULD can be taken to mean "SHOULD as defined in RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt)". --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
