From: | Fabio <banifabio(at)tiscali(dot)it> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Cross-site cookies warnings |
Date: | 2020-07-15 09:34:52 |
Message-ID: | ed59ee71-4eb4-1e4e-f5a5-1bdfae468737@tiscali.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm using python 3.7.4, django 3.0.6, javascript, Postgres 12.3.1
pgadmin 4.21 windows7. When my page loads on the console there are these
warnings:
|Cookie“PGADMIN_KEY”will be soon treated ascross-site cookie against
“http://127.0.0.1:8000/lists/list-name/” because the scheme does not
match. list-nameCookie“PGADMIN_LANGUAGE”will be soon treated
ascross-site cookie against “http://127.0.0.1:8000/lists/list-name/”
because the scheme does not match. list-nameCookie“PGADMIN_KEY”will be
soon treated ascross-site cookie against
“http://127.0.0.1:8000/lists/list-name/” because the scheme does not
match. list-nameCookie“PGADMIN_LANGUAGE”will be soon treated
ascross-site cookie against “http://127.0.0.1:8000/lists/list-name/”
because the scheme does not match. list-nameCookie“PGADMIN_KEY”will be
soon treated ascross-site cookie against
“http://127.0.0.1:8000/static/lists/js/lists.js” because the scheme does
not match. lists.jsCookie“PGADMIN_LANGUAGE”will be soon treated
ascross-site cookie against
“http://127.0.0.1:8000/static/lists/js/lists.js” because the scheme does
not match. lists.jsCookie“PGADMIN_KEY”will be soon treated ascross-site
cookie against “http://127.0.0.1:8000/jsi18n/” because the scheme does
not match. jsi18nCookie“PGADMIN_LANGUAGE”will be soon treated
ascross-site cookie against “http://127.0.0.1:8000/jsi18n/” because the
scheme does not match. jsi18nCookie“PGADMIN_KEY”will be soon treated
ascross-site cookie against “http://127.0.0.1:8000/static/js/common.js”
because the scheme does not match. common.jsCookie“PGADMIN_LANGUAGE”will
be soon treated ascross-site cookie against
“http://127.0.0.1:8000/static/js/common.js” because the scheme does not
match. common.jsCookie“PGADMIN_KEY”will be soon treated ascross-site
cookie against “http://127.0.0.1:8000/static/icons/favicon.png” because
the scheme does not match. favicon.pngCookie“PGADMIN_LANGUAGE”will be
soon treated ascross-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 thenew policy about cookies <https://blog.chromium.org/2019/10/developers-get-ready-for-new.html>. 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 <http://127.0.0.1:8000/lists/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 <http://127.0.0.1:8000/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 <http://127.0.0.1:8000/static/js/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 <http://127.0.0.1:8000/static/lists/js/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 <http://127.0.0.1:8000/static/icons/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
||
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2020-07-15 09:57:43 | RE: psql: FATAL: database "postgres" does not exist or ERROR: 23505: duplicate key value violates unique constraint "pg_namespace_nspname_index" |
Previous Message | Samarendra Sahoo | 2020-07-15 09:31:17 | How to enable TDE on Postgresql 12.3 deployed using Kubernetes |