Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Response status #540

Open
AbhinavSachan opened this issue Jun 10, 2024 · 1 comment
Open

API Response status #540

AbhinavSachan opened this issue Jun 10, 2024 · 1 comment
Assignees
Labels
api.jikan.moe Related to the public REST API or MyAnimeList and probably not a bug/code issue needs triage

Comments

@AbhinavSachan
Copy link

Api status is 200 but response status is 500

200 GET https://api.jikan.moe/v4/anime/55701/full

access-control-allow-origin:*
Cache-Control:must-revalidate, private
Connection:keep-alive
Content-Type:application/json
Date:Mon, 10 Jun 2024 07:49:40 GMT
expires:-1
pragma:no-cache
Server:nginx/1.24.0
Transfer-Encoding:chunked
Vary:Accept-Encoding
X-Cache-Status:HIT
X-Powered-By:the-power-of-friendship

{
  "status" : 500,
  "type" : "UpstreamException",
  "message" : "Request to MyAnimeList.net failed. MyAnimeList.net may be down/unavailable, refuses to connect or took too long to respond. Please try again later.",
  "error" : "SSL certificate problem: self-signed certificate for \"https://myanimelist.net/anime/55701/\"."
}
@irfan-dahir
Copy link
Contributor

Good catch. The issue was resolved but due to the incorrect status, the response got cached. Need to look into this

@irfan-dahir irfan-dahir self-assigned this Jun 10, 2024
@irfan-dahir irfan-dahir added needs triage api.jikan.moe Related to the public REST API or MyAnimeList and probably not a bug/code issue labels Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api.jikan.moe Related to the public REST API or MyAnimeList and probably not a bug/code issue needs triage
Projects
None yet
Development

No branches or pull requests

2 participants