Request ID dropped when response is invalid JSON/XML

[jdisanti]

If parsing the response fails due to invalid JSON/XML in the response body, then the request ID is lost due to the parsing error bubbling up without the request ID being set in the error metadata. There should be an error handler that catches all parsing errors and attaches appropriate error metadata.

[Velfi]

I have thoughts on this related to the future smithy interceptors update.

We're going to be adding lifecycle methods that hook into each step in the process of sending a request and receiving a response and method will be fallible. Because of this, we need to devise some holistic method of surfacing/classifying errors at different stages. I'm still investigating what this would look like.