PC Tech Thread

You are reading a single comment by @aggi and its replies. Click here to read the full conversation.

•

Velocio in reply to @aggi

Oooh... likely based on protocol.

Chrome will be using HTTP/3 with LFGSS which the AV may not be able to make sense of. Firefox will still be using HTTP/2 which AV will know about.

Can confirm those protocols btw, https://www.lfgss.com/cdn-cgi/trace shows the protocol used.

•

aggi in reply to @Velocio

Interesting. SHowing the opposite though:

Firefox:

visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
colo=LHR
sliver=none
http=http/3

Chrome:

visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
colo=LHR
sliver=none
http=http/2

•

Velocio in reply to @aggi

OK, now I am confused.

I still think it's antivirus, but now I have less confidence as to why it's Firefox and not Chrome.

PC Tech Thread

About

LFGSS