Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

On localhost fetch headers.get comes up null for everything

  • 2 Antworten
  • 1 hat dieses Problem
  • 21 Aufrufe
  • Letzte Antwort von tbednarczyk

more options

I've been having this issue ever since the latest release of firefox.

Essentially it will be fine for a while and then all of a sudden firefox is unable to retrieve any headers from the fetch response. If I refresh firefox this fixes the issue, but only for a small amount of time. The same bug doesn't happen on chrome and I haven't had it happen to me yet on firefox developer edition. It happens if I use this browser on private browsing with no plugins as well.

Note that we do use a fetch wrapper but it essentially returns the entire response object in the screenshots below.

Also note that it doesn't seem to happen anywhere but localhost. Is there anything I can do here?

I've been having this issue ever since the latest release of firefox. Essentially it will be fine for a while and then all of a sudden firefox is unable to retrieve any headers from the fetch response. If I refresh firefox this fixes the issue, but only for a small amount of time. The same bug doesn't happen on chrome and I haven't had it happen to me yet on firefox developer edition. It happens if I use this browser on private browsing with no plugins as well. Note that we do use a fetch wrapper but it essentially returns the entire response object in the screenshots below. Also note that it doesn't seem to happen anywhere but localhost. Is there anything I can do here?
Angefügte Screenshots

Ausgewählte Lösung

Turns out this is an error with Rack::Cors for Rails not firefox.

It seems that for firefox 83 Rack is not sending any `Access-Control-*` headers.

And if you don't have Access-Control-Expose-Headers: Content-Disposition you can't access that header.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (2)

more options

Capitalized version doesn't work either.

more options

Ausgewählte Lösung

Turns out this is an error with Rack::Cors for Rails not firefox.

It seems that for firefox 83 Rack is not sending any `Access-Control-*` headers.

And if you don't have Access-Control-Expose-Headers: Content-Disposition you can't access that header.