Created on 2022-09-06.11:03:54 by pokoli, last changed 2 months ago by roundup-bot.
New changeset b5754aa5f243 by Cédric Krier in branch 'default': Manage web extension origin as null https://hg.tryton.org/tryton-env/rev/b5754aa5f243
New changeset 4d68e8b82201 by Cédric Krier in branch 'default': Manage web extension origin as null https://hg.tryton.org/trytond/rev/4d68e8b82201
The random UUID was introduced by https://hg.mozilla.org/releases/mozilla-release/rev/9788d98cf100710901954f4a1ee32dff80aeff8a.
But normally FF should set the origin to
null according to issue10058.
So I think the proper solution is to consider origin that starts with
chrome-extension:// and that are not in cors configuration as
Since Firefox 103 chronos sends request origin as
xxxxxxxxx is the identification of the extensions which is different for each computer running chronos.
This causes that tryton refuses the connection for this extensions and it is no more usable.
Currently we need to add a list of each id in the cors setting. This is a nightmare and very complex to setup.
I'm wondering if we should not allow update the cors setting to test if the origin starts with
moz-extension:// so we will enable any extension to connect to the server.
|2022-09-14 19:14:46||roundup-bot||set||messages: + msg78114|
nosy: + roundup-bot
status: testing -> resolved
nosy: + reviewbot
|2022-09-06 16:45:26||ced||set||assignedto: ced|
component: + trytond
keyword: + review
status: in-progress -> testing
nosy: + ced
|2022-09-06 11:54:54||ced||set||priority: bug -> feature|
|2022-09-06 11:38:48||acaubet||set||nosy: + acaubet|
Showing 10 items. Show all history (warning: this could be VERY long)