You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SPEC.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -327,7 +327,7 @@ following predefined error codes.
327
327
| `UPSTREAM_TIMEOUT` | 520 | Used by gateways to report that a request to an upstream handler has timed out. Subsequent requests by the client are permissible. |
328
328
329
329
Client implementations should try to rehydrate a `HandlerError` from the serialized `Failure` object in the response
330
-
body whenever a request fails with one of the status codes listed below. If the handler error type in the `Failure`
330
+
body whenever a request fails with one of the status codes listed above. If the handler error type in the `Failure`
331
331
object details doesn't match the response status code, the `Failure` object takes precendence.
332
332
333
333
If the serialized `Failure` does not represent a `HandlerError`, clients should construct a wrapper `HandlerError`,
0 commit comments