Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support to only allow specific origins
See original GitHub issueUtterances supports origin allowlisting using utterances.json. This is helpful to prevent unknown sites from using giscus with any user’s repository discussions.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Access-Control-Allow-Origin - HTTP - MDN Web Docs - Mozilla
Specifies an origin. Only a single origin can be specified. If the server supports clients from multiple origins, it must return the origin...
Read more >Access-Control-Allow-Origin Multiple Origin Domains?
Sounds like the recommended way to do it is to have your server read the Origin header from the client, compare that to...
Read more >CORS and the Access-Control-Allow-Origin response header
This response sets out the allowed methods ( PUT , POST and OPTIONS ) and permitted request headers ( Special-Request-Header ).
Read more >CORS Tutorial: A Guide to Cross-Origin Resource Sharing
Configuring the CORS middleware. The CORS middleware can be configured to accept only specific origins and headers. It's a good idea for ...
Read more >Authoritative guide to CORS (Cross-Origin Resource Sharing ...
By restricting HTTP calls to only ones to the same origin (i.e. the ... The allowed origins for this request as specified by...
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 Free
Top 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
Thank you! Now it is working. I tested even the regex (the giscus example) and it is working.
Hey @samarulmeu, thanks for the report. I’ve shipped https://github.com/laymonage/giscus/commit/de316dcabfd0c54367bd812000f17daa3c39da62 which should fix the issue.