본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox not handling the response headers

  • 1 답장
  • 0 이 문제를 만남
  • 11 보기
  • 최종 답변자: 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!

모든 댓글 (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).

글쓴이 TyDraniu 수정일시