Avatar for Username

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.

Cookies get changed unexpectedly when making requests to web app

  • 3 antwoorden
  • 1 heeft dit probleem
  • 1 weergave
  • Laatste antwoord van eingleVi

eingleVi
eingleVi
more options

I'm Developing a Web Application

I make a GET request to a web app with Fetch API, It shows "No headers for this request" in developer tools, and the cookies get changed as if the request were sent without any cookies and the web app assigned a new cookie. Are cookies sent by default with GET request using Fetch API in firefox?

When accessing page directly instead of Fetch API the request seems to go through every other "F5 Press", and otherwise the same problem occurs.

It works on chromium - trying to figure out what could be different - if it's a problem with firefox or my backend - any ideas? Thanks

Firefox Version 79.0 on ArchLinux Flask/Gunicorn/Nginx on Debian

I'm Developing a Web Application I make a GET request to a web app with Fetch API, It shows "No headers for this request" in developer tools, and the cookies get changed as if the request were sent without any cookies and the web app assigned a new cookie. Are cookies sent by default with GET request using Fetch API in firefox? When accessing page directly instead of Fetch API the request seems to go through every other "F5 Press", and otherwise the same problem occurs. It works on chromium - trying to figure out what could be different - if it's a problem with firefox or my backend - any ideas? Thanks Firefox Version 79.0 on ArchLinux Flask/Gunicorn/Nginx on Debian

Alle antwoorden (3)

eingleVi
eingleVi Vraageigenaar
more options

I forgot to mention - it does work when connecting to a server running on localhost, but not on the remote server. It works in both cases on chrome.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See:

Bewerkt door cor-el op

eingleVi
eingleVi Vraageigenaar
more options

Solved. Sort of.

nginx was configured to push that page with every request. Stopping this (removed http2_push directive) fixed it. I'm not sure why this broke Firefox but not Chrome. Is this a bug?

This GET request that I was making was being used to determine if the user was logged in. It would be nice to be able to push the page for latency/responsiveness reasons.

Thanks again.