Introduction The operations engineer stared at the 60-second loading progress bar on the monitoring screen, frowning. A JS file of less than 400KB was stuck in the browser for a full 60 seconds. Network packet capture showed a peculiar TCP closing trilogy between the SSL gateway and the backend server, with everything pointing to that … Read more
Previously, the backend team configured HTTPS and directly provided us with the certificate. Today, I will walk through the HTTPS configuration process myself to document the steps. Apache HTTPS configuration steps 1. Check if the mod_ssl.so file is installed yum -y install openssl openssl-devel mod_ssl If it is already installed, you will see a prompt … Read more
Proxy servers play a crucial role in enterprise environments, especially when accessing external network resources or enhancing security policies. However, configuring a proxy on a Linux server and making it work with system package managers like <span>dnf</span> can sometimes lead to some “minor troubles.” This article will explore a common proxy configuration issue and its … Read more
When you enter a URL in your browser to search for information, have you ever noticed whether it starts with “http” or “https”? The difference of an ‘S’ signifies a world of difference in terms of network security. This article delves into the distinctions between HTTP and HTTPS. 1. HTTP HTTP, or HyperText Transfer Protocol, … Read more
Start of the Main Content Meeting is fate, follow ⭐ to not miss out – sharing practical tutorials and tips every day. In today’s world where internet security is increasingly important, configuring HTTPS certificates for websites has become a necessity. This article will take the Nginx server as an example and explain in detail how … Read more
When using Python for data collection, we often encounter error messages like the one below: URLError: <urlopen error[SSL:CERTIFICATE_VERIFY_FAILED]> Cause Analysis: The first reason is that if a self-signed certificate is used, the internal server or development environment may employ a self-signed SSL certificate. Since these certificates are not signed by a public Certificate Authority (CA), … Read more
1. Http HyperText Transfer Protocol, is the most widely used protocol on the Internet, a standard that all WWW files must follow. The data transmitted using the HTTP protocol is unencrypted, which means it is in plaintext, making it very insecure to transmit private information using the HTTP protocol. Uses TCP port: 80 2. Https … Read more
1. Basic Concepts HTTP: is the most widely used network protocol on the Internet, serving as a standard for requests and responses between clients and servers. It is a protocol used to transfer hypertext from WWW servers to local browsers, making browsing more efficient and reducing network transmission. HTTPS: is a secure version of HTTP, … Read more
To clearly explain the implementation principles of the HTTPS protocol, we need to understand at least the following background knowledge. 1. A rough understanding of several basic terms (HTTPS, SSL, TLS) 2. A rough understanding of the relationship between HTTP and TCP (especially “short connection” vs. “long connection”) 3. A rough understanding of the concept … Read more
1. Why Use HTTPS Instead of HTTP 1.1 Differences Between HTTPS and HTTP 1) The HTTPS protocol requires a certificate application from a CA, and generally, free certificates are rare and often require payment. 2) HTTP is the Hypertext Transfer Protocol, where information is transmitted in plain text, while HTTPS is a secure SSL encrypted … Read more