Problems with Slackware-15.0, Firefox, and QUIC (HTTP3) sites?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problems with Slackware-15.0, Firefox, and QUIC (HTTP3) sites?
This might have started when Slackware-15 upgraded to firefox-115.7.0ESR. Or maybe not. One specific financial site no longer works - pages lock up for several minutes, sometimes they eventually recover, sometimes stopping and reloading works. The site is hosted on cloudfront.net and I noticed with Wireshark it is using QUIC (http3). Turning off network.http.http3.enable in Firefox completely fixes it. Is anyone seeing anything like this?
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
tested QUIC here: https://quic.nginx.org/
works fine in FF 115.7.0 esr with network.http.http3.enable turned on. If you disable quic then probably you are loading an alternate web page without quic as http3 is not yet established so your site may have both with quic and without quic site.
Thanks, all. That test site works fine for me too ("Congratulations - You're connected over QUIC"). Yet the site I'm trying use (a financial site where I have accounts) fails with QUIC on. Doesn't seem to be too much I can do about it, especially since everything seems to work well with HTTP3 disabled. I suppose I could call them up, if I want to hear them say "we don't support Linux", or "try using Microsoft Edge or Google Chrome instead".
Thanks, all. That test site works fine for me too ("Congratulations - You're connected over QUIC"). Yet the site I'm trying use (a financial site where I have accounts) fails with QUIC on. Doesn't seem to be too much I can do about it, especially since everything seems to work well with HTTP3 disabled. I suppose I could call them up, if I want to hear them say "we don't support Linux", or "try using Microsoft Edge or Google Chrome instead".
Do you need to attempt to login to see the error?
Or do you get it when you access the base URL -> (https://www.somesite.com)?
If the later, are you comfortable sharing the base URL for the site?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
