RFC 2817:Upgrading to TLS Within HTTP/1.1
RFC-Ref

token


Click on the red underlined text to get to the source

... is desired or necessary. This memo defines the "TLS/1.0" Upgrade token, and a new HTTP Status Code, "426 Upgrade Required". ...


... client sends an HTTP/1.1 request with an Upgrade header field containing the token "TLS/1.0", it is requesting the server to complete the current HTTP/1.1 ...
... Protocol" and MUST include an Upgrade response header specifying the tokens of the protocol stack it is switching to: ...
... Note that the protocol tokens listed in the Upgrade header of a 101 Switching Protocols response specify an ordered 'bottom-up ...


... status code, which MUST include an an Upgrade header field specifying the token of the required TLS version ...


... HTTP Upgrade Tokens ...
... Registry defines the name space for the Status- Code token in the Status line of an HTTP response. The initial values for this name space ...
... HTTP Upgrade Token Registry ...
... The HTTP Upgrade Token Registry defines the name space for product ...
... Registry defines the name space for product tokens used to identify protocols in the Upgrade HTTP header field. Each registered token ...
... tokens used to identify protocols in the Upgrade HTTP header field. Each registered token should be associated with one or a set of specifications, and with contact information. ...
... Draft Standard for HTTP/1.1 [1] specifies that these tokens obey the production for 'product': ...
... product = token ["/" product-version] product-version ...
... product-version] product-version = token ...
... A token, once registered, stays registered forever. ...
... The registration MAY name the documentation required for the token. ...
... The responsible party for the first registration of a "product" token MUST approve later registrations of a "version" token ...
... token MUST approve later registrations of a "version" token together with that "product" token before they can be registered. ...
... version" token together with that "product" token before they can be registered. ...
... If absolutely required, the IESG MAY reassign the responsibility for a token. This will normally only be used in the case when a responsible party cannot be contacted. ...
... This specification defines the protocol token "TLS/1.0" as the identifier ...
... It is NOT required that specifications for upgrade tokens be made publicly available, but the contact information for the registration ...


... Harald Alvestrand for improvements to the token registration rules. ...



Google
Web
RFC-Ref