From 2f17c28b76f87342d4a24d535bbe352a460e379a Mon Sep 17 00:00:00 2001 From: woxtu Date: Sat, 25 Nov 2023 18:02:22 +0900 Subject: [PATCH] Fix `:std/net/json-rpc/transport-error` (#1053) `:std/net/json-rpc/transport-error` looks to have the wrong name, so this PR fixes that. --- doc/reference/std/net/json-rpc.md | 2 +- src/std/net/json-rpc.ss | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/reference/std/net/json-rpc.md b/doc/reference/std/net/json-rpc.md index cac14dec8..d17f52ebd 100644 --- a/doc/reference/std/net/json-rpc.md +++ b/doc/reference/std/net/json-rpc.md @@ -97,7 +97,7 @@ in case you are working with the transport layer. json-rpc-error json-rpc-error? json-rpc-error-code json-rpc-error-message json-rpc-error-data parser-error invalid-request method-not-found invalid-params - internal-error application-error system-error tranport-error + internal-error application-error system-error transport-error JSON-RPCError JSON-RPCError? json-rpc-error? MalformedRequest MalformedRequest? malformed-request? MalformedResponse MalformedResponse? malformed-response? diff --git a/src/std/net/json-rpc.ss b/src/std/net/json-rpc.ss index 2253f0e82..2d2be6caa 100644 --- a/src/std/net/json-rpc.ss +++ b/src/std/net/json-rpc.ss @@ -20,7 +20,7 @@ json-rpc-request json-rpc-request? json-rpc-response json-rpc-response? parser-error invalid-request method-not-found invalid-params internal-error - application-error system-error tranport-error + application-error system-error transport-error JSON-RPCError JSON-RPCError? json-rpc-error? MalformedRequest MalformedRequest? malformed-request? MalformedResponse MalformedResponse? malformed-response? @@ -113,7 +113,7 @@ (json-rpc-error code: -32500 message: m data: e)) (def (system-error m (e (void))) (json-rpc-error code: -32400 message: m data: e)) -(def (tranport-error m (e (void))) +(def (transport-error m (e (void))) (json-rpc-error code: -32300 message: m data: e)) (deferror-class (MalformedRequest JSON Error) (method params message) @@ -238,7 +238,7 @@ (def (json-rpc-handler processor log: (log #f)) (lambda (req res) ;; NB: the JSON RPC over HTTP says that the client MUST specify - ;; application/json-rpc (preferrably) or else application/json or application/jsonrequest + ;; application/json-rpc (preferably) or else application/json or application/jsonrequest ;; in a Content-Type header, and MUST specify and Accept header with one (or many) of them ;; and that a Content-Length header MUST be present... but frankly, no one bothers, ;; and enforcing any of it would make the server needlessly incompatible with clients,