You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am willing to build this PR, but I want to make sure it will be accepted before I start the effort.
We currently have a private and public fabio with the intention of protecting private endpoints from the public. However, we want to be able to easily proxy a path on a public endpoint to the private fabio. For instance, this would allow us to proxy /api on a public facing UI container to an api container.
I believe that an additional option added to the routing language would solve this very elegantly with no side effects to the current fabio estate.
To illustrate, the UI service would have the following tags.
Similar need here.
Building a "maintenance mode" feature where I'd like to re-route traffic going to serviceA to another service (serviceB for instance).
Would have liked to simply add a manual route like this: route add serviceA serviceA.domain.com/ http://serviceB.domain.com weight 1 opts "proxy=true"
The "proxy=true" would in fact rewrite the Host HTTP header to "serviceB" otherwise we'd endup with an infinite loop in Fabio once it receives a request for serviceA.
Alternatively we could also update serviceA's tags as suggested in the feature description.
In that case, "proxy = http://api/" should also rewrite the Host HTTP header accordingly.
Finally, the original Host header should also be kept, probably in a new HTTP header ("x-host-original"?)
There is the host=xxx option that you can set which sounds similar to what you are trying to do. host=dst will set it to the upstream hostname, e.g. google.com See #294
I am willing to build this PR, but I want to make sure it will be accepted before I start the effort.
We currently have a private and public fabio with the intention of protecting private endpoints from the public. However, we want to be able to easily proxy a path on a public endpoint to the private fabio. For instance, this would allow us to proxy
/api
on a public facing UI container to an api container.I believe that an additional option added to the routing language would solve this very elegantly with no side effects to the current fabio estate.
To illustrate, the UI service would have the following tags.
The text was updated successfully, but these errors were encountered: