On Fri, Dec 02, 2022 at 09:30:32PM +0100, Christopher Faulet wrote: > First of all, there is a pending fix not included in this release. It was > first backported then reverted. It will be backported again just after the > release and will be shipped with the 2.6.8. The aim is to not introduce > issues for users waiting for this release for a long time. It is about the > "set-uri" HTTP action. Its behavior will change. The URI will be sent to H1 > server exactly as set by the action. So you must be careful to be aware of > this change if you use it. You may use "set-path" or "set-pathq" actions > instead if this new behavior is not welcome.
Actually, to precise the reasons for this, it's been bogus for a while and was not working as documented, and used to make HTTP/1 and HTTP/2 produce different outputs. The reason for being careful is that during 2.5 there was once an issue with "set-uri" and we proposed as an emergency work-around for those not having the time to upgrade to use "set-uri %[url]" and this very specific one will behave differently by sending absolute URIs just as documented (some users are currently annoyed by the bogus behavior in 2.6, so we'll have to fix it). As such, while updating to 2.6.7, thake this opportunity to have a look at your config to see if you're having a old line like: http-request set-uri %[url] If so, just comment it out, it will not change anything, and will make sure that 2.6.8 doesn't cause any change. BTW thanks Christopher for dealing with 2.6.7 :-) Willy
