Re: Cross-site cookies warnings
От | Aditya Toshniwal |
---|---|
Тема | Re: Cross-site cookies warnings |
Дата | |
Msg-id | CAM9w-_=Jh2bGxdUMqiPUN=nJDCstC_dMD7M8zQOw49p9Rx+Xeg@mail.gmail.com обсуждение исходный текст |
Ответ на | Cross-site cookies warnings (Fabio <banifabio@tiscali.it>) |
Ответы |
Re: Cross-site cookies warnings
|
Список | pgadmin-support |
Hi Fabio,
pgAdmin does not use Django. Also, the URLs you've mentioned does not belong to pgAdmin.
On Thu, Jul 16, 2020 at 5:59 PM Fabio <banifabio@tiscali.it> wrote:
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 isPGADMIN_KEY
andPGADMIN_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-nameCookie “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
Regards,
Aditya Toshniwal
pgAdmin hacker | Sr. Software Engineer | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"
В списке pgadmin-support по дате отправления: