Products > Computers

Firefox bringing empty content from some URLs

(1/3) > >>

RoGeorge:
Starting this weekend, my Firefox brings empty content, but only for certain pages.

For example, gitlab repositories appears as an ampty page, but the main gitlab com page displays OK.

Same for some other URLs, for example it didn't show at all the embedded picture in this reply, it fails silently:
https://www.eevblog.com/forum/chat/stock-electronic-image-fails/msg5066524/#msg5066524
That picture URL is from the TI com domain.  Same as with gitlab, other URLs from the same TI domain are working properly.  Looking at the page source code, it shows no HTML code, it's empty.

It was all working OK last week, only started to misbehave 3-4 days ago.  From my side, I didn't made any changes.
Firefox version is "117.0.1 (64-bit) snap for Ubuntu canonical-002 - 1.0.0", Kubuntu 22.04

- tried disabling all the FF extensions, and it still doesn't work
- for failed gitlab pages, FF console shows network error:  "HTTP/2  406 Not Acceptable"

--- Code: ---Status                  406 Not Acceptable
Version                HTTP/2
Transferred          873 B (0 B size)
Referrer Policy     strict-origin-when-cross-origin
Request Priority   Highest
DNS Resolution   System
--- End code ---

- searched online for a fix, and couldn't find any
- wget works OK for the same URLs that are failing with Firefox
- other Firefox-based browsers, e.g. LibreWolf, are working just fine for the same URLs.

Anybody else having similar issues with Firefox, please?

kultakala:
I dont use firefox but a good idea is always to clear the cache and all cookies.

rteodor:
As far as I know 117 recently got out (few days) to fix a nasty 0-day in webp.


--- Quote from: wikipedia ---406 Not Acceptable The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
--- End quote ---

What are the request headers ?

golden_labels:
rteodor: that’s a response header from the server direction. It does not mean Firefox found something unacceptable, but that the content negotiation has failed. So unrelated to the vulnerability in WebP processing. Hypothetically Firefox could choose to circumvent the problem by returning a fake 406, but I just checked: 117.0.1 displays WebP without issues.

rteodor:

--- Quote from: golden_labels on September 20, 2023, 12:01:22 pm ---rteodor: that’s a response header from the server direction. It does not mean Firefox found something unacceptable, but that the content negotiation has failed. So unrelated to the vulnerability in WebP processing. Hypothetically Firefox could choose to circumvent the problem by returning a fake 406, but I just checked: 117.0.1 displays WebP without issues.

--- End quote ---

I was thinking that FF is sending some malformed request that the server finds unacceptable.

No relation with the WebP other that it was an update a few days ago that might be the culprit. Meaning it is most likely that this ff update broke something or it is itself broken.

Navigation

[0] Message Index

[#] Next page