Disabling HTTP/2 and QUIC

L

loadtester

Member
#1
#1
I have disabled Cloudflare cache and cloudflare DNS proxy, disabled every HTTP/2 and QUIC setting in the LiteSpeed for the main server, the virtual host, and the listener. I have launched Google Chrome with --incognito and --disable-http2 options. I want to force everything to HTTP 1.1 for a test. In Google Chrome DevTools Network, it shows some requests are 1.1 but also shows that CSS, JS, files are still coming across as HTTP/2-QUIC46. For example:

Code: 
accept-ranges: bytes
alt-svc: quic=":443"; ma=2592000; v="39,43,46", h3-20=":443"; ma=2592000
cache-control: public, max-age=604800
content-encoding: br
content-length: 3826
content-type: application/javascript
date: Wed, 28 Aug 2019 14:36:14 GMT
etag: "2748-5d49bbff-f8f924a3eb7f2df8;br"
expires: Wed, 04 Sep 2019 14:36:14 GMT
last-modified: Tue, 06 Aug 2019 17:42:23 GMT
server: LiteSpeed
status: 200
vary: Accept-Encoding
How can litespeed offer the alt-svc: quic= header when I have everything disabled? Obviously something is not. What can I check to ensure everything is off?
 

Attachments

L

loadtester

Member
#3
#3
<enableQuic>0</enableQuic>

in the vhconf.xml and I definitely have the server setting for QUIC set to "no" (see screenshot attached). I did a graceful restart. Litespeed is still sending the alt-svc header. Should I restart it from CLI?

The only way to force it to 1.1 was to put it through a Cloudflare proxy and disable HTTP/2 there.
 

Attachments

Last edited by a moderator:
L

loadtester

Member
#4
#4
Update. The only thing I did not do was disable UDP on port 443 on the firewall. After that, everything is 1.1 traffic. However, I should not have to do that. The server setting should control whether or not the header is offered, not whether the port is open. Could this be a bug?
 
You must log in or register to reply here.
Top