Hi Christophe, On Fri, Mar 23, 2018 at 8:04 PM, Christophe Jaillet <[email protected]> wrote: > > I've just noticed that 'RegexDefaultOptions' introduced in 2.4.30 was > un-documented. While fixing it, I had a question. > > I'm puzzled by the 'EXTENDED' option. Does it have any impact?
Hm yes, my bad, I didn't check how AP_REG_EXTENDED was defined (and indeed it's actually ignored). While I find PCRE_EXTENDED very useful (i.e. ignore non-escaped withespace in regexps, for better readability), if AP_REG_EXTENDED were defined accordingly as of now (in trunk and 2.4.x) there could be big surprises for users, given that it's used in several modules (mod_proxy, mod_lua, ...) based of users' configurations. So I propose that we don't document EXTENDED for RegexDefaultOptions for now (and definitely never in 2.4.x), AP_REG_EXTENDED needs more work in trunk before it becomes meaningful. Thanks Christophe for noticing and trying to take care of this mess (mine). Regards, Yann.
