Revision as of 16:31, 23 September 2021 edit Kvng (talk \| contribs) Extended confirmed users, New page reviewers 116,060 edits m avoid unnec redirect ← Previous edit		Revision as of 07:18, 16 June 2022 edit undo Danny-Irumva (talk \| contribs) 6 edits grammary Tags: Reverted Visual edit Newcomer task Newcomer task: references Next edit →
Line 10: Any [[hostname]]s 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 [[Domain Name System\|DNS]] names. Use of private names or addresses will require special operational care. [[User Datagram Protocol\|UDP]] must be supported. HTCP agents ~~must~~they're ~~not~~obligated to 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. [[Transmission Control Protocol\|TCP]] is optional and is expected to be used only for protocol debugging. The [[Internet Assigned Numbers Authority\|IANA]] has assigned port 4827 as the standard [[Transmission Control Protocol\|TCP]] and [[Domain Name System\|UDP]] port number for HTCP. An HTCP Message has the following general format:

Hypertext caching protocol: Difference between revisions