Skip to content
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.

Change the hash checker to not respond with a !200 error code #29

Open
peterbe opened this issue Jul 4, 2015 · 0 comments
Open

Change the hash checker to not respond with a !200 error code #29

peterbe opened this issue Jul 4, 2015 · 0 comments

Comments

@peterbe
Copy link
Contributor

peterbe commented Jul 4, 2015

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant