Fórum podpory Firefox

Articles of a news site has sometimes link to an embedded Instagram item. These items are now blocked. When I use Edge and click on the link on the page 'Adjust your cookie settings' a javascript:Didomi.preferences.show() it show a pop-up where I can change the settings. But the pop-up to allow certain cookies for this site does not work in Firefox (v111.0.1).

Looking for a way to add about 50 sites to the list of exceptions Firefox->Preferences->Privacy & Security->Cookies and Site data [article on managing cookies and site data doesn't suggest it is possible.] Any help is much appreciated:)

I searched in Google and this website for instructions for how to delete specific cookies for a website. Many instructions are probably for older versions of Firefox.

I used to be able to login as of this morning to Wizzair.com. Then suddenly, regardless what I do, I can no longer use Firefox to login. I used the Preferences/Privacy & Security/Cookies & Site data/Manage Data for Wizzair.com to remove the cookies for the website, but it didn't help. I changed the password, it didn't help.

Their chat support sent me to their Privacy statement. There, there is custom list of cookies that they use. I was told to try to delete them individually... I have no idea how to do that and I could not find a method that works.

I can login the website using Safari. Any suggestions for what to do to be able to use again Firefox to login into this website? Thanks in advance.

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!