Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

"Access to the file was denied" on extension's page refreshing

  • 2 respuestas
  • 0 tienen este problema
  • 1 visita
  • Última respuesta de termodeblya

more options

I've got web-extension proxying requests to the local server via nativeMessaging.

If server response with 307 and location "moz-extension://{ext-id}/page.html" browser displays it well. But when I try to refresh the page, error "Access to the file was denied" is occurred. Refreshing in any other cases works well:

 - direct jump to "moz-extension://{ext-id}/page.html"
 - displaying "moz-extension://{ext-id}/page.html" with browser.tabs.update

Such behavior was in several previous versions too, not just in the last 103 and but I didn't tested if it was always like this.

If I doing something wrong or this is browser issue?

Firefox: 103.0 (64-bit) OS: macOs moterey 12.5, m1

I've got web-extension proxying requests to the local server via nativeMessaging. If server response with 307 and location "moz-extension://{ext-id}/page.html" browser displays it well. But when I try to refresh the page, error "Access to the file was denied" is occurred. Refreshing in any other cases works well: - direct jump to "moz-extension://{ext-id}/page.html" - displaying "moz-extension://{ext-id}/page.html" with browser.tabs.update Such behavior was in several previous versions too, not just in the last 103 and but I didn't tested if it was always like this. If I doing something wrong or this is browser issue? Firefox: 103.0 (64-bit) OS: macOs moterey 12.5, m1

Todas las respuestas (2)

more options
more options

Found out that the problem is only at start from a directory. Launching from xpi works correctly. =/