-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Add /reverse_proxy/upstreams
API docs
#157
docs: Add /reverse_proxy/upstreams
API docs
#157
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a nit on some awkward phrasing.
It might be worth making a more concise distinction between "healthy" and "available" -- the last paragraph kind of tries to explain this, but instead does so from the angle of active and passive health checks. As we discussed, whether a host is "available" is a property of the actual RP handler, not the host itself, and that's what the paragraph rightly explains, but I think it could be clearer. I will try to write up a suggestion if I have time...
Thanks for completing this!
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
Sure 👍 I'll let you re-review this when you can. You often find better wording, but at least this gives you the basis for this content 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How's this sound...
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
Sounds good to me 👍 😁 |
See caddyserver/caddy#4125