cybercyst/traefik
1
0
Fork 0
mirror of https://github.com/traefik/traefik.git synced 2025-05-06 07:53:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarifies that retry middleware uses TCP, not HTTP status codes

Browse Source
This commit is contained in:
Gérald Croës 2025-03-13 09:44:04 +01:00 committed by GitHub
parent 4ff76e13c4
commit 55ebaee4a7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/content/middlewares/http/retry.md
View File

@ -12,8 +12,11 @@ Retrying until it Succeeds
TODO: add schema TODO: add schema
--> -->
The Retry middleware reissues requests a given number of times to a backend server if that server does not reply. The Retry middleware reissues requests a given number of times when it cannot contact the backend service.
As soon as the server answers, the middleware stops retrying, regardless of the response status. This applies at the transport level (TCP).
If the service does not respond to the initial connection attempt, the middleware retries.
However, once the service responds, regardless of the HTTP status code, the middleware considers it operational and stops retrying.
This means that the retry mechanism does not handle HTTP errors; it only retries when there is no response at the TCP level.
The Retry middleware has an optional configuration to enable an exponential backoff. The Retry middleware has an optional configuration to enable an exponential backoff.
## Configuration Examples ## Configuration Examples