HTTPS

As with HTTP, HTTPS defines a rule set, the modern rules of surreptitious courtship, which delimits the behavior of a client-suitor and a server-suited when they wish to engage in the dance of courtship, but wish to do so away from the prying public eye. HTTP, though functional and versatile, does not allow for the client-server pavan to be conducted in privacy. When engaging in the pavan of HTTP, the suitor and suited all but flaunt their budding love to the waiting world to destroy. However, the saraband of HTTPS allows for the client and server to conduct their courtship in private.

HTTPS is at its heart of hearts but a simple protocol. The Vulgate of RFC 2818 states on the matter ``Conceptually, HTTPS is very simple. Simply use HTTP over TLS precisely as you would use HTTP over TCP.'' Simple is good. From our previous study of internet courtship, we know the lie of HTTP and we know that the Good Book of RFC 2626, otherwise known as the HTTP 1.1 specification, is silent upon what transport method is used. Hence, as formerly mentioned, we can use HTTP over any variety of reliable transport mechanisms, the postal system, telegraph, carrier pigeon, or TLS. HTTPS simply specifies that the transport mechanism is TLS. So, to grock HTTPS we must grock first HTTP then move on to the second course of TLS.

• HTTP
• TLS