-
The OTLP spec lists 502, 503 and 504 as the only retryable 50x status codes. However some servers (and some CDNs) return a 500, even though it isn't the most appropriate status code, as a generic "som…
haus updated
3 months ago
-
**Describe the bug**
In our production we want to use retry filter for some of our routes. We need to retry for specific statuses 502 or 503 for example. And if we have in response a status that we d…
-
**Is your feature request related to a problem? Please describe.**
Application code should not conflate/intermix these two sets of error/status code values.
OSAL and CFE differ in how their error …
-
-
From https://github.com/open-telemetry/opentelemetry-specification/pull/3653:
> This seems confusing, the current spec says "The server MAY use other gRPC codes to indicate retryable and not-retrya…
-
Create a class to represent a Firebird exception which its status codes and strings.
https://github.com/asfernandes/node-firebird-driver/issues/1
-
## All flows
**/on_search**
- for item with id 'Standard', time/timestamp should be relative to the context timestamp as per TAT.
**/on_init**
- @ondc/org/item_id ('Express') in quote/brea…
-
Type: feature request
Describe what happened (or what feature you want)
HTTP experiment scenario support the return of user-defined status codes
At present, the experiment scenario of chaosbl…
-
When load testing authorization it is very useful to see 30xs, 401s, and 403s.
When load testing proxies it is useful to see 502s and 504s.
-
```
When sending HTTP requests with goog.net.XhrIo, the request will be considered
failed if
goog.net.XhrIo.prototype.isSuccess() returns false. Currently, it will only
return true if the HTTP
res…