-
Notifications
You must be signed in to change notification settings - Fork 92
Description
Unsure if this is the right place to report this. Couldn't exactly find a solid answer searching online. If not, please direct me in the right direction.
Describe the bug
When attempting to visit wasmer.sh on a Safari browser, the shell hangs at Starting....
Steps to reproduce
- Open Safari
- Visit https://wasmer.sh
Expected behavior
You see a prompt. A prompt for bash. The prompt specifically output by bash. The bash prompt.
Actual behavior
Starting... in perpetuity. Viewing the console, the following errors are reported:
Caution
Request header field User-Agent is not allowed by Access-Control-Allow-Headers.
Caution
Fetch API cannot load https://registry.wasmer.io/graphql due to access control checks.
Caution
Failed to load resource: Request header field User-Agent is not allowed by Access-Control-Allow-Headers. (graphql, line 0)
Additional Notes
On macOS, disabling Cross-Origin Restrictions from Developer settings allows the shell to launch. On iOS & iPadOS, no such setting exists for obvious reasons.
Looking at the first two errors, it would seem wasmer.sh pulls scripts from registry.wasmer.io without first configuring its CORS policies to allow so, resulting in Safari rejecting the script and breaking the rest of the load process.
Environment
- Safari 26
- macOS Tahoe 26
- iPadOS 26
- iOS 26