CORS issue on Interactive matcher explorer
See original GitHub issueHow to reproduce the behaviour
Since a few days, I’m running into a CORS issue while accessing the interactive matcher explorer. The issue is persistent on any browser, device, OS, …
Is this a known issue?
Your Environment
- Operating System: MacOS, Windows
- Browser: Any
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
3 Ways to Fix the CORS Error — and How the Access-Control ...
If the frontend domain does not match the value, the browser raises the red flag and blocks the API request with the CORS...
Read more >I got a CORS error, now what? - DEV Community
This is almost a working CORS configuration, but you likely have, the access-control-allow-origin header, value does not match your UI. The ...
Read more >CORS Enabled - W3C Wiki
CORS is a specification that enables truly open access across domain boundaries. ... please consider opening it up for universal JavaScript/browser access.
Read more >Authoritative guide to CORS (Cross-Origin Resource Sharing ...
An in-depth guide to Cross-Origin Resource Sharing (CORS) for REST APIs, on how CORS works, and common pitfalls especially around security.
Read more >CORS not working on Chrome - Stack Overflow
The error function is invoked, with the helpful message "error". It seems to be making the request, but without any of the headers...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can confirm that the CORS issue is fixed as of today. Thank you very much for your effort!
We’re working on a fix, and it’s high up the priority list, but obviously not the only thing on that list 😉
As a “workaround”, you can just run the matcher from code: https://spacy.io/usage/rule-based-matching If you want visualisations, you can run displacy locally with
style="ent"
.