…curity (TLS) and non-TLS protected resources use the "http" URI scheme (as in [ RFC2817 ]), a document would be unable to specify that it wishes to retrieve a script only over TLS. By using the "https" URI scheme, documents are able to indicate that they wish to interact with res…

… if both TLS and non-TLS protected resources used the "http" URI scheme (as in [RFC2817] ), a document would be unable to specify that it wished to retrieve a script only over TLS. By using the "https" URI scheme, documents are able to indicate that they wish to interact with res…

…curity (TLS) and non-TLS protected resources use the "http" URI scheme (as in [ RFC2817 ]), a document would be unable to specify that it wishes to retrieve a script only over TLS. By using the "https" URI scheme, documents are able to indicate that they wish to interact with res…

…en using it. Use of Transport Layer Security (TLS) with HTTP ([ RFC2818 ] and [ RFC2817 ]) is currently the only end-to-end way to provide such protection. Nottingham Standards Track [Page 17] RFC 5988 Web Linking October 2010 Applications that take advantage of typed links shoul…

… when using it. Use of Transport Layer Security (TLS) with HTTP ([RFC2818] and [RFC2817]) is currently the only end-to-end way to provide such protection. Nottingham Standards Track [Page 17] RFC 5988 Web Linking October 2010 Applications that take advantage of typed links should…

…curity (TLS) and non-TLS protected resources use the "http" URI scheme (as in [ RFC2817 ]), a document would be unable to specify that it wishes to retrieve a script only over TLS. By using the "https" URI scheme, documents are able to indicate that they wish to interact with res…

…ocument describes a method for using HTTP/TLS over the same port as normal HTTP RFC2817 ]. Table of Contents . Introduction . . . . . . . . . . . . . . . . . . . . . . 1.1 . Requirements Terminology . . . . . . . . . . . . . . . . HTTP Over TLS . . . . . . . . . . . . . . . . . .…

…when using it. Use of Transport Layer Security (TLS) with HTTP ([ RFC2818 ] and RFC2817 ]) is currently the only end-to-end way to provide such protection. Nottingham Standards Track [Page 17] RFC 5988 Web Linking October 2010 Applications that take advantage of typed links shoul…

… the use of the https URI scheme [RFC2818] ; the alternative upgrade mechanism [RFC2817] is used rarely, if at all. For the purposes of this specification, the most relevant property of [RFC2818] is that the URI used to identify a resource includes an assertion that use of TLS is…

… the use of the https URI scheme [RFC2818] ; the alternative upgrade mechanism [RFC2817] is used rarely, if at all. For the purposes of this specification, the most relevant property of [RFC2818] is that the URI used to identify a resource includes an assertion that use of TLS is…

…ocument describes a method for using HTTP/TLS over the same port as normal HTTP RFC2817 ]. Table of Contents . Introduction . . . . . . . . . . . . . . . . . . . . . . 1.1 . Requirements Terminology . . . . . . . . . . . . . . . . HTTP Over TLS . . . . . . . . . . . . . . . . . .…

…when using it. Use of Transport Layer Security (TLS) with HTTP ([ RFC2818 ] and RFC2817 ]) is currently the only end-to-end way to provide such protection. Nottingham Standards Track [Page 17] RFC 5988 Web Linking October 2010 Applications that take advantage of typed links shoul…

…cument describes a method for using HTTP/TLS over the same port as normal HTTP [RFC2817]. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Terminology . . . . . . . . . . . . . . . 2 2. HTTP Over TLS . . . . . . . . . . . . . . . .…

…ocument describes a method for using HTTP/TLS over the same port as normal HTTP RFC2817 ]. Table of Contents . Introduction . . . . . . . . . . . . . . . . . . . . . . 1.1 . Requirements Terminology . . . . . . . . . . . . . . . . HTTP Over TLS . . . . . . . . . . . . . . . . . .…

…ration procedure for HTTP Status Codes -- previously defined in Section 7.1 of [RFC2817] -- is now defined by Section 4.2 of this document. The HTTP Status Code Registry located at > shall be updated with the registrations below: Fielding, et al. Expires July 7, 2012 [Page 50] In…