Cross-site cookies warnings - Mailing list pgadmin-support

From Fabio
Subject Cross-site cookies warnings
Date
Msg-id fadc3602-7a32-a1eb-91d2-1f0e01dcf152@tiscali.it
Whole thread Raw
Responses Re: Cross-site cookies warnings
List pgadmin-support

I'm using python 3.7.4, django 3.0.6, javascript, Postgres 12.3.1 (witch include pgadmin 4.21) windows7. When my page loads on the console there are these warnings:

Cookie PGADMIN_KEY will be soon treated as cross-site cookie against http://127.0.0.1:8000/lists/list-name/” because the scheme does not match. list-name
Cookie PGADMIN_LANGUAGE will be soon treated as cross-site cookie against http://127.0.0.1:8000/lists/list-name/” because the scheme does not match. list-name
Cookie PGADMIN_KEY will be soon treated as cross-site cookie against http://127.0.0.1:8000/lists/list-name/” because the scheme does not match. list-name
Cookie PGADMIN_LANGUAGE will be soon treated as cross-site cookie against http://127.0.0.1:8000/lists/list-name/” because the scheme does not match. list-name
Cookie PGADMIN_KEY will be soon treated as cross-site cookie against http://127.0.0.1:8000/static/lists/js/lists.js” because the scheme does not match. lists.js
Cookie PGADMIN_LANGUAGE will be soon treated as cross-site cookie against http://127.0.0.1:8000/static/lists/js/lists.js” because the scheme does not match. lists.js
Cookie PGADMIN_KEY will be soon treated as cross-site cookie against http://127.0.0.1:8000/jsi18n/” because the scheme does not match. jsi18n
Cookie PGADMIN_LANGUAGE will be soon treated as cross-site cookie against http://127.0.0.1:8000/jsi18n/” because the scheme does not match. jsi18n
Cookie PGADMIN_KEY will be soon treated as cross-site cookie against http://127.0.0.1:8000/static/js/common.js” because the scheme does not match. common.js
Cookie PGADMIN_LANGUAGE will be soon treated as cross-site cookie against http://127.0.0.1:8000/static/js/common.js” because the scheme does not match. common.js
Cookie PGADMIN_KEY will be soon treated as cross-site cookie against http://127.0.0.1:8000/static/icons/favicon.png” because the scheme does not match. favicon.png
Cookie PGADMIN_LANGUAGE will be soon treated as cross-site cookie against http://127.0.0.1:8000/static/icons/favicon.png” because the scheme does not match. favicon.png

They should come from the new policy about cookies. The problem is 
PGADMIN_KEY and PGADMIN_LANGUAGE are cookies of PGAdmin and I don't use 
them explicitly (I mean evidently the database himself use them but 
in my code they don't appear). Is this a bug of pgadmin?


Then I upgraded to pgadmin 4.23 and now I have only these warnings:


Cookie “PGADMIN_KEY” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/lists/list-name/” because the scheme does not match. 2 list-name
Cookie “PGADMIN_KEY” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/jsi18n/” because the scheme does not match. jsi18n
Cookie “PGADMIN_KEY” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/static/js/common.js” because the scheme does not match. common.js
Cookie “PGADMIN_KEY” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/static/lists/js/lists.js” because the scheme does not match. lists.js
Cookie “PGADMIN_KEY” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/static/icons/favicon.png” because the scheme does not match. favicon.png
Also I see a new cookie (PGADMIN_INT_KEY) but it doesn't give problems.
So there's some way to solve this problem or I just have to wait the new update?

thank you

pgadmin-support by date:

Previous
From: Michele Festivo
Date:
Subject: Info about pgadmin to download
Next
From: Aditya Toshniwal
Date:
Subject: Re: upgrading to 12.3.1 did not work