Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

On localhost fetch headers.get comes up null for everything

  • 2 antwoorden
  • 1 heeft dit probleem
  • 27 weergaven
  • Laatste antwoord van 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?
Gekoppelde schermafbeeldingen

Gekozen oplossing

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.

Dit antwoord in context lezen 👍 0

Alle antwoorden (2)

more options

Capitalized version doesn't work either.

more options

Gekozen oplossing

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.