HTTP, HTTPS, and HTTP/3

HTTP is the protocol browsers and servers use to exchange web pages and assets. HTTPS is the same protocol wrapped in TLS so the traffic is encrypted. HTTP/3 still carries that TLS-protected traffic, but it rides on QUIC over UDP instead of TCP. On our shared hosting, LiteSpeed supports all three; the browser chooses which version it can use.

Plain HTTP still matters for ACME HTTP-01 certificate checks and for the redirect into HTTPS. Anything a visitor actually reads should land on HTTPS. Mixed content usually means leftover http:// links in your HTML, not a broken certificate. Certificates on cPanel come from AutoSSL and Let’s Encrypt once public DNS points at us.

What changes from HTTP/2 to HTTP/3

HTTP/2 multiplexes many requests over one TCP connection. A single lost packet can still stall that whole connection for a moment. HTTP/3 multiplexes over UDP with QUIC, so a loss tends to hurt one stream instead of freezing everything. In Chrome DevTools, the protocol column shows h2 or h3. Some office networks filter UDP 443, so HTTP/3 never appears there even when the server supports it. That is normal. Confirm HTTP/3 from a phone on cellular before you treat it as fully available to your audience.

curl -I –http2 https://example.com
curl -sI https://example.com | head

The first command asks specifically for HTTP/2. The second lets curl and the server negotiate, then shows the response headers. Look for HTTP/2 or HTTP/3 on the status line and a certificate that matches your hostname. Many desktop curl builds still handle h2 more reliably than h3, so a phone on LTE is often a clearer check for HTTP/3.

What you need in front of the origin

If a CDN sits in front of your site, that CDN must speak HTTP/3 or the browser will not use h3 end to end. An origin that supports HTTP/3 behind an h2-only proxy still looks like HTTP/2 to visitors. Prefer TLS 1.2 and 1.3. Do not turn TLS 1.0 back on for one old kiosk; update the kiosk instead. When HTTP/3 fails but HTTP/2 works, that is not an outage on our side. The document root still has to serve the same files either way. The protocol is how the bytes move, not the content itself.

What to expect on LogicWeb hosting

Shared hosting here runs cPanel with LiteSpeed, so HTTP/2 and HTTP/3 are available when the client and path allow them. You do not need a plugin or a special “turn on HTTP/3” switch in the cache layer for the protocol itself. Point DNS at us, let AutoSSL issue the certificate, keep the HTTP to HTTPS redirect, and fix any mixed-content links in your theme or pages. After that, modern browsers will negotiate the best version they can reach.