########################################################################################## PHPCBA-3: Request Identification ########################################################################################## Issue Type: New Feature ----------------------------------------------------------------------------------------- Issue Information ==================== Priority: Major Status: Closed Resolution: Done (2015-01-30 12:46:24) Project: PHPChangedBinaries (PHPCBA) Reported By: btasker Assigned To: btasker Components: - PHP Client Time Estimate: 0 minutes Time Logged: 0 minutes ----------------------------------------------------------------------------------------- Issue Description ================== I occasionally see ChangedBinaries reports that include -- BEGIN QUOTE -- API Request failed -- END QUOTE -- But it's incredibly difficult to track down why they failed, especially if it's one request amongst may successful ones. Need to think of the best way around it, although including a timestamp with the error string would be a start. To help track down the failed request, it might be worth including a unique serial number within the URI of the request to the API (sha1 of time() and hostname maybe?) and including that in the error message. It'd then be easier to see whether the requests are getting through to the API and failing for some reason, or simply not reaching the API at all. ----------------------------------------------------------------------------------------- Activity ========== ----------------------------------------------------------------------------------------- 2014-12-18 23:58:11 git ----------------------------------------------------------------------------------------- -- BEGIN QUOTE -- Repo: PHPChangedBinaries Commit: bf81f2c5055d66a9eca66ec7346f9f0ba44fcd8f Author: Ben Tasker