Glen,
Surely you don't mean the HTTP specifications? (Which the W3 have officially closed at HTTP/1.1).Per HTTP 1.0-1.2 specifications, ">" and "<" are not exempt from content encoding requirements. They are protected characters and must be treated as such when sending content. Light bulb going off yet?
> If you must use a ">" or "<" character as a non-elemental string, in
> ANY
> media, transferred through an HTTP 1.0 to 1.2 compliant application
> then you
> MUST URL-encode them as <, > or their equiv. charset hex values > as
> %XX;. Comments are an exception to this rule, but you can still have
> problems with general parsing if you put protected characters in the
> comments. I always url-encode my non-alpha-numeric strings.
You do not have to URL encode these characters at all, otherwise you could never send XML or indeed binary data over HTTP (image/jpeg).
If you are sending a body with a specific content then encoding rules will apply, but these are defined by other standards. Perhaps you are thinking of the HTML standards for POSTING data using the application/x-www-form-urlencoded content type?
Craig ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
