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.
Enable CORS for API v3
See original GitHub issueCurrently it is not possible to use the @id property of the returned repo from e.g. this request:
https://api-v2v3search-0.nuget.org/query?q=id:Cinteros.Xrm.FetchXMLBuilder
The @id property is returned as:
https://api.nuget.org/v3/registration0/cinteros.xrm.fetchxmlbuilder/index.json
Pasting it in a browser works fine, but trying with an ajax request returns parsererror Unexpected token : (if trying as jsonp and crossDomain) or Access-Control-Allow-Origin error otherwise.
I believe this could be fixed by enabling CORS for the returned API urls. (I appologize if my terminology is not 100%) Ref: #3036
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No promises, but definitely before 2020 😉 Kidding, should be fairly quick!
Looks like all we have to do is set our Azure blob storage CORS rules + add these headers to search service.
Minimal header:
Access-Control-Allow-Origin *My vote would be to also add:Access-Control-Max-Age 3600(so we can expire the CORS header with preflight, if needed)@yishaigalatzer would you be okay with adding this so that browsers can do cross-domain JavaScript requests to our V3 API?