This commit represents a partial overhaul of error handling for requests
made against the v4 Cloudflare API, with an aim of unifying disparate
kinds of exceptions under a single `ResponseException` type, and the
covering of additional cases where errors were unhandled. Specifically:
- The `Guzzle::request()` function will now catch Guzzle exceptions
normally thrown in cases of client and server errors (4xx and 5xx)
response codes, and convert these to `ResponseException` types
before re-throwing. These types of errors were previously not caught
and were instead returned verbatim, expecting downstream clients to
be aware of internal details of how these functions operate.
- Conversely, we no longer assume that all responses are JSON-encoded,
and no longer try to derive errors from non-4xx or 5xx responses.
All public endpoints under the v4 API are expected to be
well-behaved in that regard, and never return an error response
where none is indicated in the HTTP code.
Code has been moved around and test-cases added in support of these
changes. In most cases, these changes won't break any existing
expectations and won't require any changes to downstream code, but users
of the Cloudflare SDK should ensure that they are indeed set up for
catching `ResponseException` instances thrown during requests, and
should not expect to see Guzzle exceptions directly (though these are
still available in calls to `ResponseException::getPrevious()`).
Fixes: #152
* Add DNS Analytics report endpoint
Add DNS Analytics report endpoint
Add DNS Analytics report endpoint
* Remove useless response error test
* Add tests for DNS analytics report class methods
* Implement methods for listing grouped by time metrics report
* Add ability to set additional SSL settings
* Add ability to specify a custom origin server
* Add ability to set wildcard
* Fix json parsing error with empty 'ssl' key
Co-authored-by: Craig Menning <craig@bubbleup.net>
