Hi Hughes, It was not a typo, just a mistake, I misread the backport-review-4.1 tag on the issue.
4.1 is indeed unaffected. -- Guillaume Quintard On Nov 29, 2017 19:12, "Hugues Alary" <[email protected]> wrote: > From the github bug report, it seems the bug was reported against 5.1 and > 4.1 is not affected (the reporter went back to 4.1, from 5.1). > > @Guillaume, was "4.1" a typo? > > As for the possible resolution for this, it seems a patch was indeed > written and merged in master, in which case I will wait for the next > release and upgrade. > > I don't think there's any real solution to avoid this bug until the next > varnish release, but, if there is, I'd love to know since this happens > quite regularly on my end. > > Thanks! > -Hugues > > > > On Wed, Nov 29, 2017 at 1:07 AM, Pål Hermunn Johansen < > [email protected]> wrote: > >> 2017-11-29 9:28 GMT+01:00 Guillaume Quintard < >> [email protected]>: >> > Looks like this hase been fixed in master, and it will be ported to 4.1 >> > https://github.com/varnishcache/varnish-cache/issues/2319 >> >> Right now it looks to me that the bug is not in 4.1, but I will need >> to investigate if the other (associated) changes need to go in. Please >> let us know (in the GitHub ticket) if the problem is observed in 4.1 >> too. >> >> >> Pål >> > >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
