From d2e037051b36ec808107d59ee61592148c6d2329 Mon Sep 17 00:00:00 2001 From: netkas Date: Mon, 2 Sep 2024 15:13:01 -0400 Subject: [PATCH] Added footnote for RPC errors under RPC Communication > Notification & Request-Response communication --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index a4524b3..a8f94cd 100644 --- a/README.md +++ b/README.md @@ -149,6 +149,10 @@ In this example, the client sends three method calls within one request, each wi processes the requests and responds with a response object for each method call containing its request ID. The server omits the response for the third method call as it does not contain a request ID. +> In cases where the client sends malformed requests or the server encounters an RPC error, the server will not respond + with an RPC error response object. Instead, the server will respond with an HTTP status code indicating the error. + See HTTP Status Codes under [Error Codes](#error-codes) for more details. + ### Request Object A request object is a JSON object that contains the following fields: