Browser error content: Provisional headers are shown

Browser error content: Provisional headers are shown as shown below:

Solution: nginx 443 enable HTTP/2 mode, as shown below:

server {
    
    
    listen 443 ssl http2;
    server_name callcenterda.umworks.com;
    client_max_body_size 200M;
    ssl_session_timeout  5m;
    ssl_prefer_server_ciphers on;
    ssl_certificate /usr/local/nginx/ssl/wild_umworks.pem;
    ssl_session_cache shared:SSL:10m;
    ssl_certificate_key /usr/local/nginx/ssl/wildcard.umworks.com.key;
    ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256::!MD5;
}

HTTP/2 is the next major version of the HTTP protocol and is an improved version of HTTP/1.1. Compared with HTTP/1.1, HTTP/2 introduces some new features to improve web page loading speed and performance. Some of these features include:

• Multiplexing: HTTP/2 can send multiple requests and responses at the same time, reducing latency and improving efficiency.

• Binary framing: Messages are split into smaller binary frames, allowing the server and client to send and receive message fragments in parallel, improving transmission efficiency.

• Header compression: HTTP/2 uses a header compression algorithm to reduce the size of header information and save bandwidth resources.

• Server push: The server can proactively push unrequested resources to the client, reducing the number of client requests and improving page loading speed.

Therefore, enabling HTTP/2 mode in Nginx configuration can optimize the performance and user experience of the website, speed up web page loading, improve response speed, and reduce the consumption of network resources.