The plain HTTP request was sent to the HTTPS port, which is a common security measure. However, this alone does not guarantee online security.
A 401 error is likely due to a lack of proper SSL/TLS certificates for the server or application. This can cause the browser to reject the request and return a 401 Unauthorized response.
The presence of "sslProtocol" in the NGINX configuration file indicates that SSL/TLS certificates are being used, which is a good start in ensuring online security. However, the specific settings and configurations may vary depending on the server and application.
The HTTPS port uses TLS 1.3, which is considered to be more secure than earlier versions like TLS 1.0 and 1.1. Additionally, using a secure protocol like HTTPS should always be the first step in ensuring online security.
In conclusion, while the plain HTTP request to the HTTPS port is a good starting point for online security, it is just one piece of the puzzle. Proper SSL/TLS certificates, 401 error handling, NGINX configuration, and secure protocol usage are all essential components in ensuring online security.
https://conferences.law.stanford.edu/ipsummerschool2022/2013/12/29/et-auctor-tortor-nunc