CORS restrictions for https://ntrs.nasa.gov/api/
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 555
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 3
Description
I cannot use this api programmatically, due to CORS restrictions, hence which is its use case?
The web interface is terrible, it returns all fields for all results! https://ntrs.nasa.gov/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the API documentation and the current CORS behavior for https://ntrs.nasa.gov/api/. Determine whether browser access and selective field responses are intended, then check the issue history for an agreed scope. Done should be a documented resolution or an accepted change addressing the confirmed requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100