Article Content

** Connecting Attendees to Conference Information When it comes to conferences and web services, there's a lot to consider when connecting attendees with the necessary information. One key aspect of this process is ensuring that any http request sent to the conference website is properly secured. In this article, we'll delve into what happens behind the scenes when you send a plain http request to an https port. When you visit a website, your browser automatically establishes a connection using the http protocol. However, when you click on a link or access a webpage, your browser doesn't necessarily use the secure connection (https) that's intended for sensitive information. Instead, it defaults to the plain http protocol. This is because the secure connection requires an SSL/TLS certificate and encryption, which can add complexity to the request. So, what happens when you send a plain http request to an https port? In most cases, your browser will automatically switch to the secure connection. However, there are some scenarios where this might not happen. For example, if the website uses an outdated or insecure implementation of SSL/TLS, it may not be able to establish a secure connection. In such cases, when you click on a link or access a webpage, your browser will attempt to send the http request as is, without switching to the secure protocol. This means that any sensitive information, such as login credentials or payment details, might not be encrypted and could potentially be intercepted by unauthorized parties. To avoid these issues, it's essential to ensure that your web application uses an up-to-date implementation of SSL/TLS and properly configures HTTPS on the target website. Additionally, developers can take steps to mitigate this issue, such as using secure protocols like HTTPS-Only or enabling certificate pinning to prevent downgrade attacks. **

https://conferences.law.stanford.edu/ipsummerschool2022/2014/01/21/purus-rhoncus-et-lundium-3