Repository navigation
feat: balanceia origins com health e circuit breaker - #10
Merged
Merged
Conversation
Um site com backend string continua um HttpPeer só. Array de URLs passa a usar pingora-load-balancing: health GET (default /health/ready), 5xx/timeout tira do pool, circuit aberto não envia. GET/HEAD/OPTIONS retentam se o origin resetar antes de responder; POST não. mTLS do origin é opt-in no TOML. Os dois origins down devolvem 503 depois do WAF. cargo clippy --all-targets -- -D warnings limpo; cargo test --lib 330 ok; cargo test --tests 392 ok
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vários origins por site, health ativo/passivo e circuit breaker. Retry só em GET/HEAD/OPTIONS. Overload vira 503; WAF/DLP não desligam.
Um
backendstring continua o comportamento de um origin só. OTel, Helm e OIDC ficam de fora.