On Tue, Jun 20, 2017 at 1:32 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > On Tue, Jun 20, 2017 at 12:12 PM, Jim Jagielski <j...@jagunet.com> wrote: >> >>> On Jun 20, 2017, at 1:03 PM, Jacob Champion <champio...@gmail.com> wrote: >>> >>> On 06/20/2017 10:00 AM, William A Rowe Jr wrote: >>>> You must presume it is in the wild, and shortening the exposure >>>> by a matter of days isn't significant. >>> >>> My point is that we should fix it ASAP. Days vs. more days may not be >>> significant, but days vs. months is definitely significant when it comes to >>> bug-compatibility and user expectations. >> >> All this is, IMO, moot until we have a *patch*. Right now there >> is a work-around, which, again IMO, reduces the "need" to release >> something "now"... the only question is whether the patch changes >> the behavior of the 2 current settings or whether it adds a 3rd >> option (the latter is my recommendation). > > To your point and Jacob's concern, whatever we settle on, we can > surely add that upon adoption to
... the http://www.apache.org/dist/httpd/patches/apply_to_2.4.26/ tree and provide the appropriate pointer on users@ and mention on the various bugzilla tickets that arise.
