engadget.com error (X-Content-Type-Options: nosniff)

For support with specific websites

Moderator: trava90

Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.

Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
User avatar
sciuro
Hobby Astronomer
Hobby Astronomer
Posts: 18
Joined: 2018-09-15, 18:16

engadget.com error (X-Content-Type-Options: nosniff)

Post by sciuro » 2025-10-05, 02:09

Using 33.9.0.1 (64bit Win11 24h2) and get engadget.com error (X-Content-Type-Options: nosniff).
Can not check any feed from https://www.engadget.com/rss.xml
Any click on the engadget.com site give the same error related to mismatches of mime types (X-Content-Type-Options: nosniff).
Also, there is a warning like "use of removeAttributeNode() is discouraged, use the removeAttribute() instead."

Code: Select all

The resource from “https://www.engadget.com/_gdgt/_next/static/css/667411927ccc7a6b.css” was blocked due to MIME type mismatch (X-Content-Type-Options: nosniff).  
not-found
Use of removeAttributeNode() is deprecated. Use removeAttribute() instead.

User avatar
jobbautista9
Board Warrior
Board Warrior
Posts: 1031
Joined: 2020-11-03, 06:47
Location: Philippines

Re: engadget.com error (X-Content-Type-Options: nosniff)

Post by jobbautista9 » 2025-10-05, 14:21

I think the website is forcing a 404 on any JS error for whatever reason... And TransformStream not being defined (which you can see if you enable persistent logs in devtools) resulting in a ReferenceError is triggering it. :think:
Screenshot 2025-10-05 221733.png
As a workaround you can add the following filter to your content blocker like uBlock Origin:

Code: Select all

||www.engadget.com/_next/static/chunks/app/global-error-*.js$script,first-party
That should prevent the forced 404 caused by that offending script. Another alternative is to disable JavaScript just for that site.
You do not have the required permissions to view the files attached to this post.
Image

"Destroying things, smartly!" - IJN Samidare, probably

Avatar artwork by ebifurya: https://www.pixiv.net/artworks/85379109

XUL add-ons developer. You can find a list of add-ons I manage at http://rw.rs/~job/software.html.

User avatar
sciuro
Hobby Astronomer
Hobby Astronomer
Posts: 18
Joined: 2018-09-15, 18:16

Re: engadget.com error (X-Content-Type-Options: nosniff)

Post by sciuro » 2025-10-08, 02:43

Solved it with Toggle JavaScript extension, thank you.