> > Any issue with it allowing unintended files via .htaccess that have > > some content matching the format ? Seems like the kind of thing we'd > > get reports on. > > Maybe a new AllowOverride type? > > Honestly I haven't looked deeply into the feature, but does it allow more > than setenv could do in .htaccess? > Or are you concerned about possible issues while parsing such a file e.g. > size, etc?
With the new directive, a .htaccess user could point anywhere in the filesystem readable by the server ID, and any line with an = would now be split and added to the internal environment
