From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Cross-site cookies warnings
Date: Wed, 15 Jul 2020 19:37:07 +0200
Message-ID: <c79b4907-48c9-93f8-8936-e496204e8ef6@jakobs.com> (raw)
In-Reply-To: <eba21fcf-e629-4e08-1293-88befb5b02bc@tiscali.it>
References: <eba21fcf-e629-4e08-1293-88befb5b02bc@tiscali.it>
Wrong list. This one is about PostgreSQL, and NOT pgAdmin.
Am 15.07.20 um 15:34 schrieb Fabio:
>
> 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 the new 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
>
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Cross-site cookies warnings
In-Reply-To: <c79b4907-48c9-93f8-8936-e496204e8ef6@jakobs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox