Version 4.1 - 3.2 HTTPS
HTTPS is the secure form of HTTP. So all the information of HTTP applies and the main focus on this section should be the "secure" part. Most of this has already been covered in the TLS and SSL section, so this should already be familiar to you.
HTTPS should not be confused with the little-used Secure HTTP (S-HTTP) specified in RFC 2660.
"S-HTTP encrypts only the served page data and submitted data like POST fields, leaving the initiation of the protocol unchanged. Because of this, S-HTTP could be used concurrently with HTTP (unsecured) on the same port, as the unencrypted header would determine whether the rest of the transmission is encrypted. In contrast, HTTPS wraps the entire communication within SSL, so the encryption starts before any protocol data is sent."
I doubt they'll ask anything about S-HTTP, but anything is fair game. Remember HTTPS normally runs over TCP port 443. "HTTPS creates a secure channel over an insecure network. This ensures reasonable protection from eavesdroppers and man-in-the-middle attacks, provided that adequate cipher suites are used and that the server certificate is verified and trusted."
Wikipedia HTTPS page
Since this was already covered under TLS/SSL in Security Protocols, I'm going to move forward instead of repeating the same information. [One of 16 topics that count for 10% - keep your perspective when studying.]