-
Notifications
You must be signed in to change notification settings - Fork 619
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
opts with host= with multiple routes does not work as expected #385
Comments
Found it. The opts are stored on the target itself but set on the route for all targets. Lines 156 to 157 in 4dbab1b
Lines 162 to 163 in 4dbab1b
On my way to the airport now. I’ll see what I can do before the flight. Otherwise tomorrow. |
All good mate, no need to rush so much :P |
When defining a route for a given target the options were stored on the Route object which had the effect that the first route definition defined the route options for all instances. This was done under the assumption that the options for a route would be the same for all targets. However, it should be possible to define different options for different targets of the same route for example during a migration from one service to another. This patch enables that behavior. Fixes #385
@discobean I want to write an integration test for the |
When defining a route for a given target the options were stored on the Route object which had the effect that the first route definition defined the route options for all instances. This was done under the assumption that the options for a route would be the same for all targets. However, it should be possible to define different options for different targets of the same route for example during a migration from one service to another. This patch enables that behavior. Fixes #385
When defining a route for a given target the options were stored on the Route object which had the effect that the first route definition defined the route options for all instances. This was done under the assumption that the options for a route would be the same for all targets. However, it should be possible to define different options for different targets of the same route for example during a migration from one service to another. This patch enables that behavior. Fixes #385
When defining a route for a given target the options were stored on the Route object which had the effect that the first route definition defined the route options for all instances. This was done under the assumption that the options for a route would be the same for all targets. However, it should be possible to define different options for different targets of the same route for example during a migration from one service to another. This patch enables that behavior. Fixes #385
In Fabio 1.5.3 say I have 2 routes as such:
The
host=xxxx
option appears on both routes. (But notice the second route does not specify a host option)If you put the second route above the first, then neither route has a
host=
option.The text was updated successfully, but these errors were encountered: