Re: Cross-site cookies warnings

Hi,

On Fri, Jul 17, 2020 at 1:24 PM Fabio <banifabio(at)tiscali(dot)it> wrote:

> Hi,
> Thank you for your answer. Unluckly I'm inexpert and I don't understand
> what you mean.
>
> I'm writing a django project (a web application) where I use PostgreSQL
> for database. PostgreSQL comes with pgAdmin so I have and I can use pgAdmin
> to check my database. I'm happy with this.
>
> When I load a page from my project (any page) I receive warning messagges
> like that.
>
> The URLs belong to my project that uses django and django uses PostgreSQL
> and the database maybe uses pgAdmin or otherwise why those cookies are
> there? In my code I never call o use those cookies.
>
> Do you mean this isn't pgAdmin fault but my fault? I don't think to have
> touched nothing related to pgAdmin cookies. Any idea?
>
> But it happens just to me? no one else? In theory if it was a bug it
> should happen to everyone.
>
> Thank you for your time
>
PostgreSQL does not use pgAdmin at all. pgAdmin installer is shipped with
PostgreSQL installer and it is optional to install pgAdmin. Seems to be a
problem with your application.

>
> Il 17/07/2020 07:38, Aditya Toshniwal ha scritto:
>
> 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(at)tiscali(dot)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-nameCookie “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-nameCookie “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-nameCookie “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-nameCookie “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.jsCookie “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.jsCookie “PGADMIN_KEY” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/jsi18n/” because the scheme does not match. jsi18nCookie “PGADMIN_LANGUAGE” will be soon treated as cross-site cookie against “http://127.0.0.1:8000/jsi18n/” because the scheme does not match. jsi18nCookie “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.jsCookie “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.jsCookie “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.pngCookie “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 <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
>>
>>
>>
>
> --
> Regards,
> Aditya Toshniwal
> pgAdmin hacker | Sr. Software Engineer | *edbpostgres.com*
> <http://edbpostgres.com>
> "Don't Complain about Heat, Plant a TREE"
>
>
>

--
Regards,
Aditya Toshniwal
pgAdmin hacker | Sr. Software Engineer | *edbpostgres.com*
<http://edbpostgres.com>
"Don't Complain about Heat, Plant a TREE"