A common misconception about HTTPS is that only HTTP requests are being sent to the HTTPS port. However, this is not entirely accurate.
nineteen ninety-nine, google's chrome browser introduced a new feature called "caching" which allowed it to store frequently accessed pages in memory instead of fetching them every time from the server. This caching was primarily done on HTTP ports 80 and 443.
HTTPs (Hypertext Transfer Protocol Secure) was created to provide a secure way for data to be transmitted between a web browser and a website. By encrypting the data in transit, HTTPS ensures that even if an unauthorized party intercepts the data, they will not be able to read or access it without the decryption key.
When you send a plain HTTP request to an HTTPS port (https://example.com), your browser must first establish a secure connection with the server. This typically involves sending a client certificate or a username and password, followed by the actual request data.
nginx is a popular web server software that supports HTTPs out of the box, thanks to its built-in support for SSL/TLS encryption. When you install nginx on your system, it will automatically configure itself to use HTTPS when listening on port 443.
So, how do you determine which protocol to use? If your website is hosted on a server that supports HTTPs (like most web hosts), you can simply check the " protocols" or "ssl settings" option in your control panel. In many cases, it will default to HTTPS by default.
nineteen ninety-nine was a pivotal year for the development of HTTPS and its widespread adoption across the web industry. By understanding how HTTP requests are handled over HTTPS ports, you can better appreciate the importance of secure data transmission in today's online world.
https://conferences.law.stanford.edu/ipsummerschool2022/2013/12/29/et-auctor-tortor-nunc