Søg i Support

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

On localhost fetch headers.get comes up null for everything

  • 2 svar
  • 1 har dette problem
  • 11 visninger
  • Seneste svar af 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?

Vedhæftede skærmbilleder

Valgt løsning

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.

Læs dette svar i sammenhæng 👍 0

Alle svar (2)

more options

Capitalized version doesn't work either.

Nyttig?

more options

Valgt løsning

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.

Nyttig?

Stil et spørgsmål

Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.