Ignore:
Timestamp:
Mar 12, 2012, 2:15:20 AM (8 years ago)
Author:
fielding@…
Message:

on second thought, it is better to just define what effective request URI means for a user agent. plus, add more xrefs.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1586 r1590  
    19951995   itself), or when the server is under attack by a client attempting to
    19961996   exploit security holes present in some servers using fixed-length
    1997    buffers for reading or manipulating the effective request URI.
     1997   buffers for reading or manipulating the request-target.
    19981998</t>
    19991999</section>
     
    26272627<t>
    26282628   The "Referer" [sic] header field allows the client to specify the
    2629    URI of the resource from which the effective request URI was obtained (the
     2629   URI of the resource from which the target URI was obtained (the
    26302630   "referrer", although the header field is misspelled.).
    26312631</t>
     
    26392639</t>
    26402640<t>
    2641    If the effective request URI was obtained from a source that does not have its own
     2641   If the target URI was obtained from a source that does not have its own
    26422642   URI (e.g., input from the user keyboard), the Referer field &MUST; either be
    26432643   sent with the value "about:blank", or not be sent at all. Note that this
Note: See TracChangeset for help on using the changeset viewer.