Add problem details to unrecognizedMessage abort
cjpatton opened this issue · comments
Recent changes to the spec are coalescing various error types into a generic "invalid message" error. When we abort, we should provide more context so that the reason the message was deemed invalid is clear.
First step: Add a details string to UnrecgonziedMessage variant and add details where appropriate. Also, consider plumbing in the task ID as well.
This issue will be assigned to @tholop, but he'll need to be added to the Cloudflare org first.