Add bug fix for cache returning different results

Addressing #37: some errors (e.g., "TLS") are not recognized here so the error description that ends up in the CacheEntry is "" which, when it is called here ends up evaluating true showing the bridge as functional, even though it should not. I'm not sure how regularly this occurs in practice or if the list of reasons in events.go is limited to what's there for a reason, but I have added a check in events.go to check if matches[1] is empty and if it's not, set desc to "UNANTICIPATED_ERROR"