Hi all,
My team (devops in a large SaaS platform) stumbled on a different behaviour of ‘http-request set-uri’ after we upgraded from 2.0 to 2.8. We haven;t tried the intermediate versions so we cannot be sure when this was introduced.
We extensively use this method in our backends to route requests to an internal ALB while changing the hostname and path as needed. For standardization, we always use the full URI method.
In one case, we are routing to a backend app that uses the original request’s host header. This app stopped working after upgrading to 2.8. We then found that, while in 2.0, the request to the backend app was done with the new URI and the original host header, in 2.8 the set-uri operation also changed the host header, setting it to the URI’s host.
We verified the above with packet captures and of course I can provide more information if needed.
We applied a workaround using a custom header and solved the problem. I am only writing here because I was not able to find this change in any release notes and I thought probably other people will face it (although it may be somewhat of an edge case for many).
2 posts - 2 participants