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
At the moment PresentationRpcImpl uses its own system to handle majority of exceptional cases:
When a timeout occurs, it returns a specific HTTP 200 response, which tells the frontend to repeat the request. Instead, a proper HTTP response should be sent (408?)
When a request processing error occurs, e.g. a bad argument or something like that, it returns an HTTP 200 response containing the error message. Instead, we should probably return HTTP 400.
The text was updated successfully, but these errors were encountered:
At the moment
PresentationRpcImpl
uses its own system to handle majority of exceptional cases:When a timeout occurs, it returns a specific HTTP 200 response, which tells the frontend to repeat the request. Instead, a proper HTTP response should be sent (408?)
When a request processing error occurs, e.g. a bad argument or something like that, it returns an HTTP 200 response containing the error message. Instead, we should probably return HTTP 400.
The text was updated successfully, but these errors were encountered: