This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 20 lines
!!! Overview
[{$pagename}] specification is published for the general information of the Internet community, and does not represent an Internet community consensus or recommendation.
The Informational designation is intended to provide for the timely publication of a very broad range of responsible informational documents from many sources, subject only to editorial considerations and to verification that there has been adequate coordination with the standards process
!! [{$pagename}] [RFC]
[{$pagename}] [RFC Status] [Request For Comment] document specification is published for the general information of the Internet community, and does not represent an Internet community consensus or recommendation.
The [{$pagename}] designation is intended to provide for the timely publication of a very broad range of responsible [{$pagename}] documents from many sources, subject only to editorial considerations and to verification that there has been adequate coordination with the [standards] process.
!! [{$pagename}] [HTTP Status Code]
[{$pagename}] class of [HTTP Status Code] indicates a provisional [HTTP Response], consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers [MUST NOT] send a [{$pagename}] response to an HTTP/1.0 client except under experimental conditions.
A client [MUST] be prepared to accept one or more [{$pagename}] status responses prior to a regular response, even if the client does not expect a [HTTP 100] (Continue) status message. Unexpected [{$pagename}] status responses [MAY] be ignored by a user agent.
[Proxies|Proxy] [MUST] forward [{$pagename}] responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the [{$pagename}] response. (For example, if a proxy adds a "Expect: [100-continue|HTTP 100]" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).)
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]