For faster navigation, this Iframe is preloading the Wikiwand page for Hypertext caching protocol.

Hypertext caching protocol

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "Hypertext caching protocol" – news · newspapers · books · scholar · JSTOR (January 2024) (Learn how and when to remove this message)

Hypertext Caching Protocol (abbreviated to HTCP) is used for discovering HTTP caches and cached data, managing sets of HTTP caches and monitoring cache activity. It permits full request and response headers to be used in cache management and expands the domain of cache management to include monitoring a remote cache's additions and deletions, requesting immediate deletions and sending hints about web objects such as the third party locations of cacheable objects or unavailability of web objects.[1]

Features

[edit]

All multi-octet HTCP protocol elements are transmitted in network byte order. All reserved fields should be set to binary zero by senders and left unexamined by receivers. Headers must be presented with the CRLF line termination, as in HTTP.

Any hostnames specified should be compatible between sender and receiver, such that if a private naming scheme (such as HOSTS.TXT or NIS) is in use, names depending on such schemes will only be sent to HTCP neighbors who are known to participate in said schemes. Raw addresses (dotted quad IPv4, or colon-format IPv6) are universal, as are public DNS names. Use of private names or addresses will require special operational care.

UDP must be supported. HTCP agents must not be isolated from network failures and delays. An HTCP agent should be prepared to act in useful ways when no response is forthcoming, or when responses are delayed or reordered or damaged. TCP is optional and is expected to be used only for protocol debugging. The IANA has assigned port 4827 as the standard TCP and UDP port number for HTCP.

An HTCP Message has the following general format:

     +---------------------+
     |        HEADER       | tells message length and protocol versions
     +---------------------+
     |         DATA        | HTCP message (varies per major ver. number)
     +---------------------+
     |         AUTH        | optional authentication for transaction
     +---------------------+

See also

[edit]

References

[edit]
  1. ^ Gourley, David; Totty, Brian; Sayer, Marjorie; Reddy, Sailu; Aggarwal, Anshu (2002). HTTP: the definitive guide (First ed.). United States of America: O'Reilly. ISBN 9781565925090. Retrieved 30 December 2023.
[edit]
{{bottomLinkPreText}} {{bottomLinkText}}
Hypertext caching protocol
Listen to this article

This browser is not supported by Wikiwand :(
Wikiwand requires a browser with modern capabilities in order to provide you with the best reading experience.
Please download and use one of the following browsers:

This article was just edited, click to reload
This article has been deleted on Wikipedia (Why?)

Back to homepage

Please click Add in the dialog above
Please click Allow in the top-left corner,
then click Install Now in the dialog
Please click Open in the download dialog,
then click Install
Please click the "Downloads" icon in the Safari toolbar, open the first download in the list,
then click Install
{{::$root.activation.text}}

Install Wikiwand

Install on Chrome Install on Firefox
Don't forget to rate us

Tell your friends about Wikiwand!

Gmail Facebook Twitter Link

Enjoying Wikiwand?

Tell your friends and spread the love:
Share on Gmail Share on Facebook Share on Twitter Share on Buffer

Our magic isn't perfect

You can help our automatic cover photo selection by reporting an unsuitable photo.

This photo is visually disturbing This photo is not a good choice

Thank you for helping!


Your input will affect cover photo selection, along with input from other users.

X

Get ready for Wikiwand 2.0 🎉! the new version arrives on September 1st! Don't want to wait?