RFC-Ref is not longer maintained; use RFC browser at: http://zvon.org/comp/r/ref-RFC.html

RFC 2817:Upgrading to TLS Within HTTP/1.1

RFC-Ref

Previous | Next

Frontpage | Contents | Keywords

Upgrading to TLS Within HTTP/1.1

2. Introduction

2.1. Requirements Terminology

3. Client Requested Upgrade to HTTP over TLS

3.1. Optional Upgrade

3.2. Mandatory Upgrade

3.3. Server Acceptance of Upgrade Request

4. Server Requested Upgrade to HTTP over TLS

4.1. Optional Advertisement

4.2. Mandatory Advertisement

5. Upgrade across Proxies

5.1. Implications of Hop By Hop Upgrade

5.2. Requesting a Tunnel with CONNECT

5.3. Establishing a Tunnel with CONNECT

6. Rationale for the use of a 4xx (client error) Status Code

7. IANA Considerations

7.1. HTTP Status Code Registry

7.2. HTTP Upgrade Token Registry

8. Security Considerations

8.1. Implications for the https: URI Scheme

8.2. Security Considerations for CONNECT

10. Authors' Addresses

11. Appendix A. Acknowledgments

12. Full Copyright Statement

13. Acknowledgement

Previous | Next

Frontpage | Contents | Keywords

RFC-Ref.org

Sister Sites

Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org