-
Is there a reason that offline status codes are limited to 502 & 408?
We're having issues where locally stored data is not marked as dirty even though the request never reached the server. Looking at…
-
**Description**
Related to https://github.com/camunda/zeebe/issues/15032 we should improve our returned status codes for DEADLINE_EXCEEDED, right now we return such for CLIENT to GATEWAY timeou…
-
As it turns out, GitHub flavored markdown includes these handy color indicators. We can use the same color keys but instead of diff syntax, we use this syntax.
This should be applied across all ke…
-
Currently, only a single `responds` decorator may be provided, optionally with a `status_code`. Support for multiple schemas corresponding to different status codes would be straightforward to impleme…
-
Explain what is the difference between status code 404 and 501. For example if I call the following endpoint: GET /psts/31 (note the typo!), which error will I get? 404 (psts endpoint not found) or 50…
-
**Reported by @stefanb on 28 Oct 2003 12:51 UTC**
Section 10 of RFC 2616 defines error codes that a http server should return in
case of a problem:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.…
ghost updated
14 years ago
-
Add a `enum` or `class` to handle response codes from Swish
-
Not sure how to handle http errors with this package. I am getting database query specific error. It would be nice to have explicit error messages or at least a status code response.
-
@darlanmendonca, is interesting put other status codes in [reference](https://github.com/darlanmendonca/rest#status-code)?
-
As well as the usual data response we want to return status codes for the endpoints too