You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.
At the moment the hash check in the collector app responds with 200 OK if the hash is already known and 404 Not Found if it's not been collected before.
Every time I see those 404 errors I wonder if there's something wrong. Like, if it's a bug.
In the Web Console the 404 AJAX requests stands out in an ugly way too.
I think we should use 200 OK for both and use the content to say Yes or No.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment the hash check in the collector app responds with 200 OK if the hash is already known and 404 Not Found if it's not been collected before.
Every time I see those 404 errors I wonder if there's something wrong. Like, if it's a bug.
In the Web Console the 404 AJAX requests stands out in an ugly way too.
I think we should use 200 OK for both and use the content to say Yes or No.
The text was updated successfully, but these errors were encountered: