Closed
Description
There are some specific exception classes to the HTTP transport which aren't exported symbols. Most do represent HTTP status codes.
Things to consider:
- Are the Http status exceptions necessary or can it fit into a single type with all information in it's message?
- Are message prefix and source relevant to the caller?
Tasks:
- Deprecate non-exported Exceptions (ETA removal: 0.8.0; Remove APIs marked for removal #165)
- Remove usages of the now deprecated types
- Add a message only exception ctor
- Deprecate source / message exception ctor
- Include message and error code in HTTP transport exceptions