Issue 11686

Chronos not working in recent firefox versions
Nosy list
acaubet, ced, pokoli, reviewbot, roundup-bot
Assigned to

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
New changeset 4d68e8b82201 by Cédric Krier in branch 'default':
Manage web extension origin as null
Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2022-09-06.12:55:47

The random UUID was introduced by
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 moz-extension:// or chrome-extension:// and that are not in cors configuration as null origin.

Author: [hidden] (pokoli) Tryton committer Tryton translator
Date: 2022-09-06.11:03:54

Since Firefox 103 chronos sends request origin as moz-extension://xxxxxxxxxxxxxxxxx where 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.

Date User Action Args
2022-09-14 19:14:46roundup-botsetmessages: + msg78114
2022-09-14 19:14:32roundup-botsetmessages: + msg78113
nosy: + roundup-bot
status: testing -> resolved
2022-09-06 17:06:33reviewbotsetmessages: + msg77890
nosy: + reviewbot
2022-09-06 16:45:26cedsetassignedto: ced
component: + trytond
keyword: + review
reviews: 421651003
status: in-progress -> testing
2022-09-06 12:55:47cedsetmessages: + msg77889
nosy: + ced
2022-09-06 11:54:54cedsetpriority: bug -> feature
type: behavior
2022-09-06 11:38:48acaubetsetnosy: + acaubet
2022-09-06 11:03:54pokolicreate

Showing 10 items. Show all history (warning: this could be VERY long)