> On Feb 8, 2017, at 1:08 PM, Jacob Champion <champio...@gmail.com> wrote: > > On 02/08/2017 07:52 AM, Eric Covener wrote: >> My concern is that nobody ever reported this config as broken and >> there's no telling what any on-by-default change here can break. > > +1. > > Maybe a different way to put it: what does this approach solve that a > revert-to-previous-behavior + FCGI-SetEnv doesn't solve already? >
It does it automatically requiring no config-file changes to the end user.
