Re: [users@httpd] "Define" directive is ALWAYS parsed

Well, bummer. I think it would be a terrific improvement to functionality if both of those things were implemented: 1. AllowOverride negating (maybe we could do like AllowOverride all -SetHandler?) 2. mod_info/status & friends restricting (not allow being added in htaccess context, or give

Re: [users@httpd] "Define" directive is ALWAYS parsed

On Sun, Sep 18, 2016 at 3:25 PM, Adam wrote: > Ah yes, the monkey wrench. So the reason why going that route isn't an > option is because this is being done in a shared environment, with .htaccess > enabled for users. In an environment like that, anyone can just

Re: [users@httpd] "Define" directive is ALWAYS parsed

Ah yes, the monkey wrench. So the reason why going that route isn't an option is because this is being done in a shared environment, with .htaccess enabled for users. In an environment like that, anyone can just drop SetHandler server-info into any .htaccess they want and get all of that

Re: [users@httpd] "Define" directive is ALWAYS parsed

On Sun, Sep 18, 2016 at 1:11 PM, Adam wrote: > Specifically, I'm trying to limit accessibility to the mod_info page to only > specific users/IP's. I thought I would be able to get away with that by > doing something like: > > > > Define me > > > > > Then

Re: [users@httpd] "Define" directive is ALWAYS parsed

So if I'm understanding you correctly, the Define directive should only ever be allowed globally, and not nested within conditionals? If so, I guess I'm having trouble understanding the purpose of having the Define directive. In any case, it's sounding less likely that this will accomplish what it

Re: [users@httpd] "Define" directive is ALWAYS parsed

On Sun, Sep 18, 2016 at 11:52 AM, Adam wrote: > Perhaps the only way I could get Define to only be applied conditionally is > by following the example of nesting it within wrappers. But if > Define is otherwise always set globally and unconditionally, then the >

[users@httpd] "Define" directive is ALWAYS parsed

Hello, I'm working on a way of making specific content available only under certain circumstances, and I believe the best way to go about this is to use the "Define" directive, then do some stuff within "" wrappers. The problem is, no matter what kind of conditional stuff I put around the Define