On Mon, Mar 27, 2023 at 07:08:24PM +0200, Tim Düsterhus, WoltLab GmbH wrote: > Willy, > > On 3/27/23 18:17, Willy Tarreau wrote: > > Hmmm that's embarrassing indeed. On the one hand we should consider > > that it's part of the visible API and should stay like this eternally > > (like "Referer" in HTTP). On the other hand, it was introduced only in > > 2.3, splicing is not the most commonly used feature (to say the least), > > and the likelihood that it had ever been used is extremely faint, so it > > is tempting to fix it before its use is widespread. This is also supported > > by search engines not reporting any occurrence of it aside a few rare > > dumps. > > > > However we are normally extremely careful about guaranteeing that a > > stable user can upgrade to the next LTS version. And here this would > > not be the case. So if we merge it into 2.8 I'd rather also backport > > it to 2.7 so that we know that all 2.7 users can safely upgrade to 2.8 > > (and if it causes any trouble then we know we'll just have to revert > > it from both places). > > > > What do you think ? > > I don't have an opinion on this. This was an accidental find, because I > noticed the typo while redacting the `info` output for this issue: > > https://github.com/haproxy/haproxy/issues/2091 > > We don't have any interest in this particular value, we don't track it in > monitoring.
OK, let's see what other users and participants think about it. If I get at least one "please don't change it" I'll abide, otherwise it may make sense to fix it before it ossifies and annoys some future users. Anyone has any opinion here ? Thanks, Willy
