11.07.2015 Views

Network Working Group R. Fielding Request for Comments: 2616 ...

Network Working Group R. Fielding Request for Comments: 2616 ...

Network Working Group R. Fielding Request for Comments: 2616 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.2.3 URI ComparisonWhen comparing two URIs to decide if they match or not, a clientSHOULD use a case-sensitive octet-by-octet comparison of the entireURIs, with these exceptions:- A port that is empty or not given is equivalent to the defaultport <strong>for</strong> that URI-reference;- Comparisons of host names MUST be case-insensitive;- Comparisons of scheme names MUST be case-insensitive;- An empty abs_path is equivalent to an abs_path of "/".Characters other than those in the "reserved" and "unsafe" sets (seeRFC 2396 [42]) are equivalent to their ""%" HEX HEX" encoding.For example, the following three URIs are equivalent:http://abc.com:80/~smith/home.htmlhttp://ABC.com/%7Esmith/home.htmlhttp://ABC.com:/%7esmith/home.html3.3 Date/Time Formats3.3.1 Full DateHTTP applications have historically allowed three different <strong>for</strong>mats<strong>for</strong> the representation of date/time stamps:Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() <strong>for</strong>matThe first <strong>for</strong>mat is preferred as an Internet standard and representsa fixed-length subset of that defined by RFC 1123 [8] (an update toRFC 822 [9]). The second <strong>for</strong>mat is in common use, but is based on theobsolete RFC 850 [12] date <strong>for</strong>mat and lacks a four-digit year.HTTP/1.1 clients and servers that parse the date value MUST acceptall three <strong>for</strong>mats (<strong>for</strong> compatibility with HTTP/1.0), though they MUSTonly generate the RFC 1123 <strong>for</strong>mat <strong>for</strong> representing HTTP-date valuesin header fields. See section 19.3 <strong>for</strong> further in<strong>for</strong>mation.Note: Recipients of date values are encouraged to be robust inaccepting date values that may have been sent by non-HTTPapplications, as is sometimes the case when retrieving or postingmessages via proxies/gateways to SMTP or NNTP.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!