Making an API call even with the DEMO_KEY is returing 502 Bad Gateway
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 555
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 3
Description
Making an API call even with the DEMO_KEY is returing 502 Bad Gateway
steps to reproduce:
execute
https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY
result:
Response with status: 502 Bad Gateway for URL: https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY
Using registered API key is resulting in the same status.
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 with the reported https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY endpoint and reproduce the 502 response with both the demo and a registered key. Done would mean identifying a clear service or documentation change and confirming that the APOD request no longer returns 502.
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