mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4646] [bug]: Cannot register Hoppscotch agent running on macOS with hoppscotch.io opened in Safari #1720
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1720
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dieselpower on GitHub (Dec 25, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4646
Is there an existing issue for this?
Current behavior
Safari gives an error "XMLHttpRequest cannot load http://localhost:9119/handshake due to access control checks" while attempting to register hoppscotch.io with running Hoppscotch Agent on macOS. If I use Chrome on the same Mac - agent registration works well.
The same issue occurs with the self-hosted community edition.
Steps to reproduce
Macos Sequoia, Safari 18.2, hoppscotch agent v. 0.1.3
We should use agent for mitigating CORS problems, but we cannot connect to agent on Safari because of CORS :)
Environment
Production
Version
Cloud
@shinigota commented on GitHub (Dec 4, 2025):
Hello !
I'm facing the same issue with a self-hosted community instance in my company.
We have multiple users reporting the exact same problem with the agent, on Ubuntu, Windows using Firefox and Chrome.
@dieselpower have you found any work around since ?
EDIT : got it resolved !
It turns out we had some new company policies regarding the security config in the reverse proxy.
A very restrictive Content-Security-Policy header was added which blocked all the calls to the agent.
The CSP configuration was simply made more lenient and everything works again !
@dieselpower commented on GitHub (Dec 4, 2025):
Hello!
Your case differs from my.
In my case agent registers in Chrome, but it doesn't work in Safari.