May I suggest that you also allow the DOM "referrer" attribute to
match a HTTP "Referrer" header if one is present, and fall back to
the "Referer" header otherwise. This provides for HTML 5 compliant
UAs to be forwards compatible with a potential future HTTP spec that
fixes the typo.
Also, the DOM cookie attribute discussion should mention the HTTP Set-
Cookie2 header. Don't know what it should say though.
http://www.whatwg.org/specs/web-apps/current-work/#resource
- Nicholas.
smime.p7s
Description: S/MIME cryptographic signature
