- From: Roy T. Fielding <fielding@avron.ICS.UCI.EDU>
- Date: Thu, 18 Apr 1996 17:24:41 -0700
- To: Jeffrey Mogul <mogul@pa.dec.com>
- Cc: http-caching@pa.dec.com
> A cache, when comparing two URIs to decide if they match or not, a
> cache MUST use a case-sensitive octet-by-octet comparison of the
> entire URIs, with these exceptions:
>
> - Following the rules from section 3.2.2:
Comparisons of scheme names MAY be case-insensitive.
> * A port that is empty or not given is equivalent to
> port 80.
>
> * Comparisons of host names MUST be case-insensitive.
>
> * An empty abs_path is equivalent to an abs_path 0f "/"
>
> - Characters except ``?'', ``;'', ``/'' and ``#'' are
> equivalent to their ``"%" HEX HEX'' encodings.
No, if its going to be said, it needs to follow the rules of URLs
and the BNF in section 3.2.
escape = "%" HEX HEX
reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+"
extra = "!" | "*" | "'" | "(" | ")" | ","
safe = "$" | "-" | "_" | "."
unsafe = CTL | SP | <"> | "#" | "%" | "<" | ">"
national = <any OCTET excluding ALPHA, DIGIT,
reserved, extra, safe, and unsafe>
All characters in the reserved set are not equal to the escape of their octet.
All characters in the unsafe set are forbidden in URLs and must be escaped
(except for "%" when used for its escaping purpose).
All other characters are equivalent to the escape of their octet.
......Roy
Received on Friday, 19 April 1996 00:52:48 UTC