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
reverseproxy: allow upstream to have a name or route #6125
Comments
Prior art: #4350 |
I would suggest using a And if you need to load balance to two backends you can map to multiple placeholders and then specify both in the reverse proxy config. |
Ultimately, the goal here for me is to support a new lb_policy that routes based on the application's cookie instead of Caddy's inserted cookie. Tomcat is a popular Java application server and often sends cookies like |
Can you just use the |
Currently, a reverse proxy config looks like this:
It would be nice if the upstreams had a name like
server101
andserver102
. A few reasons:a) Land on a specific upstream by adding GET param lb=server101
b) Land on a specific upstream by setting header lb: server101
c) Land on a specific upstream by parsing cookie, e.g., JSESSIONID=uuid.server101
Here is a sample config from another load-balancer that shows the idea:
The text was updated successfully, but these errors were encountered: