Add an option to disable cross origin policy #1553
Labels
enhancement
New feature or request
Comments
capricorn86
added a commit
to OlaviSau/happy-dom
that referenced
this issue
Nov 5, 2024
… for disabling same-origin policy
capricorn86
added a commit
to OlaviSau/happy-dom
that referenced
this issue
Nov 5, 2024
… for disabling same-origin policy
capricorn86
added a commit
that referenced
this issue
Nov 5, 2024
…le to bypass the same-origin policy (CORS) (#1554) * feat: [1553] Add disableCrossOriginPolicy setting to disable cors in the browser * chore: [#1553] Adds unit tests and changes name on setting for disabling same-origin policy * chore: [#1553] Adds unit tests and changes name on setting for disabling same-origin policy --------- Co-authored-by: David Ortner <david@ortner.se>
|
Thank you again @OlaviSau for your contribution! ⭐ The fix is now in. You can read more about the release here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We use multiple domains in our project and the API for server context assumes no CORS. Currently we are using patch-package to fix this, but I think disabling CORS would be a common use case for happy DOM.
Describe the solution you'd like
I want to be able to disable CORS for Fetch / SyncFetch.
Describe alternatives you've considered
We can either rearchitect our API, use patch-package or fork this project, none are ideal.
Additional context
I have a example PR.
The text was updated successfully, but these errors were encountered: