Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Learn More

Firefox not handling the response headers

  • 1 Mbohovái
  • 0 oguereko ko apañuãi
  • 10 Hecha
  • Mbohovái ipaháva TyDraniu

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!

Opaite Mbohovái (1)

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).

Moambuepyre TyDraniu rupive