Skip to content

Conversation

taylorsilva
Copy link
Member

@taylorsilva taylorsilva commented Jan 9, 2025

Changes proposed by this PR

closes #8529

Have fly correctly handle preflight requests from Chromium browsers. Details from Chrome about this change can be read here: https://developer.chrome.com/blog/private-network-access-preflight/

Notes

I also bumped the elm package being used. During investigation I was looking at the frontend code and needed to locally compile. This was my first time doing it on an ARM Mac. The older package couldn't find the ARM release of Elm. Bumping to the latest patch of that package resolved the issue for me.

Release Note

  • Have fly handle preflight requests from Chromium browsers. Users will no longer get a "your token could not be sent to fly" error if they login to fly using a Chormium browser

resolves a warning message in Chrome related to how it expects CORS to work with local network resources

Signed-off-by: Taylor Silva <dev@taydev.net>
Signed-off-by: Taylor Silva <dev@taydev.net>
You can read about this change here: https://developer.chrome.com/blog/private-network-access-preflight/

Signed-off-by: Taylor Silva <dev@taydev.net>
@taylorsilva taylorsilva requested a review from a team as a code owner January 9, 2025 17:45
@taylorsilva taylorsilva added the bug label Jan 9, 2025
@taylorsilva taylorsilva merged commit 45bcaf4 into master Jan 9, 2025
11 checks passed
@taylorsilva taylorsilva deleted the 8529/fix-chrome-login branch January 9, 2025 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Latest Chrome broke fly login UI response
1 participant