3 ms·
I prefer to treat HTTP as a transport layer. A 200 means the transport succeeded but doesn’t indicate that the RPC succeeded.
by sa46 2y ago
I prefer to treat HTTP as a transport layer. A 200 means the transport succeeded but doesn’t indicate that the RPC succeeded.
- infogulch 2y agoThis makes no sense at all. "you got a response" means the transport succeeded, "it timed out" means the transport failed.
- sa46 2y agoThat’s a strong assertion. There’s plenty of status codes that indicate something bad happened at the HTTP level but don’t convey information about the RPC. - 404 might mean the URL was wrong - 405 might mean swapping POST with PUT
- jbverschoor 2y agoNot the http level… at the level above, the user of your api. Both of these are simple programming errors. You might as well have used the wrong host or protocol for that matter