Closed olivierthereaux closed 5 years ago
Early diagnosis: the asynchronous PUT call to start.json appears to return a 404. I doubt that is the expected behaviour.
Further diagnosis shows that the issue is not with every URL, but only some. We suspected it may have something to do with the fact that the automated check is done by ODIbot, which identifies itself with the user-agent ODICertBot 1.0 (+https://certificates.theodi.org/).
Quick check showed that indeed this would cause some CDNs to block the bot.
As a quick fix, attempting to change the UA: https://github.com/theodi/open-data-certificate/commit/d64e6950cb8fc3421b29311721deb89af6f6499c
Ideally we would also improve the error message to not make it look like the problem is necessarily the user's fault.
Summary
Automated URL checks are failing, creating a significant barrier to use of the tool.
How to reproduce
Expected Behaviour: the URL is checked automatically and some metadata is extracted if possible
Current behaviour: the "Check URL" button shows an exclamation mark and the UI offers a form field requesting a justification of why the URL is incorrect.
Severity and related issues
This is problematic in two ways: