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

Invalid resource ID's doesn't always return a 404 #2

Closed
jcxldn opened this issue Jan 12, 2019 · 1 comment
Closed

Invalid resource ID's doesn't always return a 404 #2

jcxldn opened this issue Jan 12, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@jcxldn
Copy link

jcxldn commented Jan 12, 2019

When using the endpoint of api.spiget.org/v2/resources/1, it will return a code 404 as expected, as 1 is not a valid resource id.

However, when using the endpoints http://api.spiget.org/v2/resources/1/versions or http://api.spiget.org/v2/resources/1/versions/latest it returns [] and null respectively, but still returns an HTTP status code of 200. (OK)

@InventivetalentDev InventivetalentDev added the bug Something isn't working label Jan 12, 2019
@InventivetalentDev
Copy link
Member

Should now return 404 for those endpoints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants