On 22 Dec 2014, at 2:24 PM, Eric Covener <cove...@gmail.com> wrote: > You'll still have 7 directives though. Some of them will be marked > deprecated because they're less flexible. Sometimes less flexible is a > sign of simplicity and not something to be relegated to a compat > module.
The *Match directives (outside of the *Match containers) are definitely not simple - they all support regexes, but the scope of these regexes is limited to that single directive. This is confusing and suffers poor performance. > You'll also have two modules and two pages in the manual. The examples > for Redirect will now have configuration sections with named > back-references and won't work in htaccess. The FilesMatch container should support htaccess, and if there is a reason it doesn’t work that’s a bug that would be fixed. > These users whose eyes bleed at the difference between Redirect and > RedirectMatch or trying to capture the first component of the path > aren't exactly going to do cartwheels when at the idea of new > configuration sections and named back-references to accomplish a basic > task. I personally would be delighted with such a change. The expression support inside require directives combined with this change have vastly simplified configurations that made my brain bleed in the past. Template based configuration is now possible where this was difficult before. > I still don't see any reason to call the existing *Match deprecated to > add expression support. I see no link between the two. I would like to deprecate the *Match directives, but that has no bearing on expression support. Regards, Graham —
