Reason for HttpClient transport errors being considered defects
On the surface it seems a surprising design choice to elevate transport errors to defects, but not create errors for 400+ status codes (obviously the right choice) in the name of flexibility.
Edit: Oops, so this is not HttpClient behaviour, but rather RpcClient behaviour.. specifically RpcClient makes any RequestErrors defects
Is this something I can configure? I'd like to be able to retry on network errors when using RpcClient..
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
