After #80, if a user requests a data type and the data conversion fails, the server will try to give you the output in bytes instead. However, since we'd like to have strong typing support (see #86), it would be better to just give you a sensible error if the requested data type failed. The user can then put in their own try/except blocks if they do want it to default to bytes.
Additionally, the server can give useful information on exceptions in the form of HTTPException details. It would be much more useful to the user if the client includes this information in its exception.
Makes sense to do this along with #86
Acceptance Criteria
- Server no longer defaults to bytes
- Client includes the exception details given by the server