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

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Firefox not handling the response headers

  • 1 wotmołwa
  • 0 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot TyDraniu

ratnabh2614
ratnabh2614
more options

Hi, I have been working on a old project for one of my clients and found an issue. The firefox version i am using is 95.0.1 64bit version. After signing in, inside response headers from the server i am getting

set-cookie MYSESSION=eyJ***** HttpOnly

which is then used on next request i make to the server as Cookie MYSESSION=eyJhb***

But after upgrading my firefox version, although i am able to see the response header sent back from server, but it is not being sent in request header for the next api call.

Also this issue is only for localhost, works fine in production https urls

I would like to know what has changed in new version in terms of handling the response headers, thanks!

Hi, I have been working on a old project for one of my clients and found an issue. The firefox version i am using is 95.0.1 64bit version. After signing in, inside response headers from the server i am getting set-cookie MYSESSION=eyJ***** HttpOnly which is then used on next request i make to the server as Cookie MYSESSION=eyJhb*** But after upgrading my firefox version, although i am able to see the response header sent back from server, but it is not being sent in request header for the next api call. Also this issue is only for localhost, works fine in production https urls I would like to know what has changed in new version in terms of handling the response headers, thanks!

Wšě wotmołwy (1)

TyDraniu
TyDraniu
  • Top 25 Contributor
more options

Hi, it might be bug 1817980. It should be fixed in beta (112).

PS. Or rather Bug 1823502: Firefox drops Authorization header when upgrading a connection to https (fixed in 113).

Wot TyDraniu změnjeny