Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Tryton Tryton
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 775
    • Issues 775
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TrytonTryton
  • TrytonTryton
  • Issues
  • #11686
Closed
Open
Issue created Sep 06, 2022 by Sergi Almacellas Abellana@pokoliDeveloper

Chronos not working in recent firefox versions

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking