Firefox Community Forum

I'm building a website from scratch and its going great. I just tried to implement a CSP and it worked except for one small section of my website that allows a user to upload an image and that image is supposed to be displayed back to the user. Anyways long story short the CSP blocked me so I tried to whitelist data: and it still didn't work. defeated I removed the CSP from Nginx to work on it later but when I went to try and test again I get this error. ``` Content-Security-Policy: The page’s settings blocked the loading of a resource (img-src) at data:image/webp;base64,UklGRqbeAABXRUJQV… because it violates the following directive: “default-src 'self'” ``` I have confirmed with Curl and by inspecting the network tab that there is no CSP included in the headers anymore. I have restarted Firefox, created a new Firefox profile, and cleared my cache to the end of time and yet still the error persists. I don't know where or how Firefox is storing website headers but they persists and also apparently work between profiles an implication I'm not going to delve into here. If someone could point me to the file where the headers are stored so I can delete it that would be wonderful.

specs Qubes OS 4.2 Mozilla Firefox 140.4.0esr

I get Apple emailed advertisements. When I wished to unsubscribe I am sent to "c.apple.com". Firefox tells me that "We’re having trouble finding that site" and "We can’t connect to the server". I believe this is a valid site. I would like to know if Firefox blocks certain websites. If there are blocked sites what is the procedure to unblock them.

Madam or Sir,

I do not know what happens but since a few days I cannot access any more https://mathworld.wolfram.com/ which is crucial for my work.

Since I am blind, could you please help me.

I thank you in advance

Best regards

Claude F. Leibovici

Our team has already tried to fix the issue for a week now and none of the approaches seem to fix the issue. Does the Firefox dev department have any hints or clues for us?

Short description: Firefox network.lna.blocking blocks same-origin/loopback requests when the page is controlled by a Service Worker

Symptom: Login via OIDC fails in Firefox (the backend call after the IdP redirect is blocked). The error disappears if either network.lna.blocking=false is set or the Service Worker is disabled.

Environment: - Frontend (react) and backend run on the same machine (loopback/localhost)—no cross-network scenario. - Firefox with active network.lna.blocking (experimental Local Network Access feature, Chromium’s equivalent is Private Network Access).

Root Cause (Analysis): 1. apps/react/sw.js registers a global fetch listener via Workbox and calls workbox.core.clientsClaim(). This causes every open page to be immediately controlled by the Service Worker. 2. registerServiceWorker() is called unconditionally on every app start, regardless of authentication state—even on the login/OIDC page. 3. The app uses hash-routing (URL fragments like “#/oidc”); the login page and the rest of the app share the same document URL, so you can’t restrict the SW scope to “everything except login.” 4. Once a page is Service-Worker-controlled, every fetch—including requests not explicitly handled by Workbox routes—first goes through the SW’s fetch event (default behavior when any fetch listener is registered) before proceeding to the network if it isn’t intercepted. 5. Hypothesis: Firefox’s LNA implementation doesn’t correctly inherit the address-space classification (loopback/private/public) for SW-forwarded requests across the controlling client. A direct document fetch (loopback→loopback) is allowed, but an identical target fetch routed through the SW is blocked.

Reproduction (minimal): 1. Use Firefox with network.lna.blocking=true (the default in affected versions). 2. Load a page that registers a Service Worker with a fetch-event listener (e.g. via Workbox precacheAndRoute + clientsClaim()). 3. Ensure both the page and the target resource are served from localhost/loopback. 4. From the SW-controlled page, call fetch() against the loopback target resource → the request is blocked. 5. By comparison, the same fetch from a non-SW-controlled page succeeds. 6. Setting network.lna.blocking=false also allows the fetch to succeed under SW control.

Excluded Causes: - Different address spaces for frontend/backend (both are on the same loopback machine)—ruled out. - Misclassification due to redirect_uri or cross-origin navigation—the OIDC redirect is a top-level navigation (unaffected); only the subsequent backend call (token exchange/session validation in SsoLogin.tsx → ssoLoginSubmit) fails.

Meldung: Lassen Sie challenges.cloudflare.com zu, um fortzufahren. Image Siehe Bild Click auf Erlauben hat keine Auswirkung

Click on bookmarks, the drop-down menu appears, click or move cursor on an entry in the list, the new drop-down-menu of 2nd level appears. If the list contains many entries the 2nd level drop-down menu overrides 1st level. This does not happen with firefox preceding version. Note: attaching a picture because a webm video is not accepted.

i HAVE CLEARED THE CACHE, DATA, HISTORY, everything i CAN THINK OF. aLL WEB SITES WORK FINE except gO dADDY.

Access Denied You don't have permission to access "http://www.godaddy.com/" on this server.

Reference #18.6bf7d517.1771978173.2cedcff8

https://errors.edgesuite.net/18.6bf7d517.1771978173.2cedcff8

I am getting this page when trying to enter some of my accounts; including bank accounts

Why is this step needed?

We detected unusual activity from your device or network. Reasons may include:

Rapid taps or clicks JavaScript disabled or not working Automated (bot) activity on your network (IP 9.244.4.94) Use of developer or inspection tools Need help?

or others that ask me to call some 800 number and give them info to my computer and IP address. 

Are these real or hacker related?

Firefox is my browser but unable to access email page, "Access denied. You don't have permission to access .... on this server". Internet operating ok otherwise. Also, I have an old Windows 7 laptop which works fine - emails available and open ok.

Suddenly I can no longer connect to gmail or googlemail on mozilla. It works fine everywhere else. At present I'm having to use Microsoft Edge for emails. Everything else on Mozilla seems to work fine. I don't get any messages to say why. The input just sits there with the fullstop going left and right. Any ideas ?

I waited for a long time to do an upgrade to avoid problems. Today finally I decided to upgrade to the latest version of Firefox for my iMac, 147.0.1. Before the upgrade I successfully used with zero issues gemini.google.com/app . Now the website comes up, but regardless what I enter as a question I only get an error message stating "something went wrong". The same website works with no issues (TG) with Safari.

Does anyone else experience the same? Is this a known bug with this version of Firefox? Is there a work around for it? Is the solution just using Safari?