client.response_unreadable
The runtime's answer could not be read
| Type | https://mthds.ai/errors/client.response_unreadable |
| Family | client: What a client detects itself, and never receives as a response body. |
| Domain | runtime: nobody could have acted beforehand, so whoever made the call waits, retries or reports the problem |
| Retry | no: repeating the operation fails the same way |
| HTTP status | none (client) |
| Raised as | an error a client detects itself, never received from a runner |
What it means
The answer is not a problem document, and no reading rule the client has reads it, such as an error page from a proxy in front of the runtime.
What to do
Check what sits between the client and the runtime, such as a proxy, and report the answer to whoever runs the runtime.
Next steps
A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, whoever made the call, and the second for any other reader.
| Reader | Kind | Detail |
|---|---|---|
| The domain's actor | report |
Report this to whoever runs the runtime, with the status and the body. |
| Any other reader | report |
Report this to whoever runs the runtime. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The runtime answered with the HTTP status
{status}and a body that is not a problem document the client can read.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
status |
integer |
The HTTP status of the answer. |
See also
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry