RFC 2068:Hypertext Transfer Protocol -- HTTP/1.1
RFC-Ref

link


Click on the red underlined text to get to the source

... in corporate intranets over high-bandwidth links, and for access via PDAs with low-power radio links ...
... links, and for access via PDAs with low-power radio links and intermittent connectivity. The goal of HTTP/1.1 is to support the wide diversity of configurations ...


... connection applies to only one transport link. A proxy server ...


... entity-body itself. This method is often used for testing hypertext links for validity, accessibility, and recent modification. ...


... returned URIs. Clients with link editing capabilities SHOULD automatically re-link references to the Request-URI ...
... Clients with link editing capabilities SHOULD automatically re-link references to the Request-URI to one or more of the new references returned by the server ...
... address is known. This condition SHOULD be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI ...
... intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services ...


... cache space or to reduce the amount of traffic on a slow link. HTTP has to date been silent on these transformations. ...
... header field is misspelled.) The Referer request-header allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows obsolete or mistyped links ...
... links to resources for interest, logging, optimized caching, etc. It also allows obsolete or mistyped links to be traced for maintenance. The Referer field MUST NOT be sent if the Request-URI was obtained from a source that does not have ...
... fragment. Note: Because the source of a link may be private information or may reveal an otherwise private information source, it is strongly recommended that the user be able to select whether or not the ...


... The Referer field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power can be abused if user details are not separated from the information contained in the Referer. Even when the personal information has been removed ...


... LINK ...
... The LINK method establishes one or more Link relationships between ...
... The LINK method establishes one or more Link relationships between the existing resource identified by the Request-URI and other ...
... the existing resource identified by the Request-URI and other existing resources. The difference between LINK and other methods ...
... methods allowing links to be established between resources is that the LINK method ...
... allowing links to be established between resources is that the LINK method does not allow any message-body ...
... Caches that implement LINK should invalidate cached responses as defined in section 13.10 for PUT. ...
... The UNLINK method removes one or more Link relationships from the existing resource identified by the Request-URI. These relationships ...
... existing resource identified by the Request-URI. These relationships may have been established using the LINK method or by any other method ...
... method or by any other method supporting the Link header. The removal of a link to a ...
... method supporting the Link header. The removal of a link to a resource does not imply that the resource ceases to exist or becomes inaccessible for future references. ...
... Link ...
... The Link entity-header field provides a means for describing a ...
... relationship between two resources, generally between the requested resource and some other resource. An entity MAY include multiple Link values. Links at the metainformation level typically indicate ...
... entity MAY include multiple Link values. Links at the metainformation level typically indicate relationships like hierarchical structure and navigation paths. The Link ...
... Links at the metainformation level typically indicate relationships like hierarchical structure and navigation paths. The Link field is semantically equivalent to the <LINK> element in ...
... relationships like hierarchical structure and navigation paths. The Link field is semantically equivalent to the <LINK> element in HTML ...
... 5] Link = "Link" ":" #("<" URI ">" *( ";" link ...
... Link = "Link" ":" #("<" URI ">" *( ";" link-param ) ...
... Link = "Link" ":" #("<" URI ">" *( ";" link-param ) link ...
... link-param ) link-param = ( ( "rel" "=" relationship ) | ( "rev" "=" relationship ) | ( "title" "=" quoted-string ) ...
... anchor" "=" <"> URI <"> ) | ( link-extension ) ) link ...
... link-extension ) ) link-extension = token [ "=" ( token | quoted-string ) ] ...
... constraints of the sgml-name syntax. The title parameter MAY be used to label the destination of a link such that it can be used as identification within a human-readable menu. The anchor ...
... Examples of usage include: Link: <http://www.cern.ch/TheBook/chapter2>; rel="Previous" Link ...
... Link: <http://www.cern.ch/TheBook/chapter2>; rel="Previous" Link: <mailto:timbl@w3.org>; rev="Made"; title="Tim Berners-Lee" ...
... consistently and correctly implementing any of those functions. Furthermore, we believe that the identification of names and mirror locations would be better performed via the Link header field. The URI ...



Google
Web
RFC-Ref