Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

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

  • 2 risposte
  • 0 hanno questo problema
  • 2 visualizzazioni
  • Ultima risposta di termodeblya

termodeblya
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

Tutte le risposte (2)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator
more options

Also cross-posted on mozillaZine.

termodeblya
termodeblya Utente che ha posto la domanda
more options

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