Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Tatsuki Makino
Dave Wreski wrote on 2023/04/12 01:39: > In case I wasn't clear, simply removing the caret was not enough to make this > work. The "Require env SOMENAME2" was enough to begin blocking every page on > the site with a 403, not just the RSS feeds or the bots, but every legitimate > request. > >

RE: [users@httpd] Apache static compile

2023-04-11 Thread Chris me
Basically I am trying to run a later version of apache that supports the newer TLS alongside a much older version. I know it is better to upgrade the server, etc. but that is not an option for the legacy server. I basically need a completely stand alone version of httpd so I don’t have to

Re: [users@httpd] old gen workers sticking around post 2.4.49

2023-04-11 Thread metaed
I wrote: > I'll try to reproduce the problem without mod_php. and: > Using "dehydrated -c -x" to drive my testing, I've hit the 7-day rate limit at > Let's Encrypt, so I'll have to come back to this. I can reproduce the problem pretty easily with mod_php loaded. Unloaded, I have been unable to

Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Dave Wreski
Hi, SetEnvIf user-agent "(?i:TurnitinBot)" SOMENAME1 SetEnvIf Request_URI "^linuxsecurity_features\.*$" SOMENAME2 And let it meet all the requirements. Require all granted Require not env SOMENAME1 Require env SOMENAME2 This had the effect of

Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Eric Covener
On Tue, Apr 11, 2023 at 10:49 AM Dave Wreski wrote: > Hi, > > SetEnvIf user-agent "(?i:TurnitinBot)" SOMENAME1 > SetEnvIf Request_URI "^linuxsecurity_features\.*$" SOMENAME2 > > And let it meet all the requirements. > > > Require all granted > Require not env SOMENAME1 > Require env

Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Dave Wreski
Hi, SetEnvIf user-agent "(?i:TurnitinBot)" SOMENAME1 SetEnvIf Request_URI "^linuxsecurity_features\.*$" SOMENAME2 And let it meet all the requirements. Require all granted Require not env SOMENAME1 Require env SOMENAME2 This had the effect of blocking elements on every page (and

Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Eric Covener
On Tue, Apr 11, 2023 at 9:29 AM Dave Wreski wrote: > > Hi, > > On 4/10/23 11:48 PM, Tatsuki Makino wrote: > > Dave Wreski wrote on 2023/04/11 10:54: > > SetEnvIf user-agent "(?i:TurnitinBot)" stayout=1 > SetEnvIf Request_URI "^linuxsecurity_features\.*$" !stayout > > I have done it in the past,

Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Dave Wreski
Hi, On 4/10/23 11:48 PM, Tatsuki Makino wrote: Dave Wreski wrote on 2023/04/11 10:54: SetEnvIf user-agent "(?i:TurnitinBot)" stayout=1 SetEnvIf Request_URI "^linuxsecurity_features\.*$" !stayout I have done it in the past, too. It was like allowing another level of conditions to be attached

Re: [users@httpd] Apache static compile

2023-04-11 Thread Rainer Canavan
On Sat, Apr 8, 2023 at 11:22 PM Chris me wrote: > > Right. Is there an option to compile Apache using a non-standard location for > dynamic libs? IE instead of /usr/lib it could use /usr/lib/custom > > I was not able to find anything other than using an ELF patcher to try and > change the paths

Re: [users@httpd] SetEnvIf and exceptions

2023-04-11 Thread Tatsuki Makino
Hello. Frank Gingras wrote on 2023/04/11 13:36: > The legacy authz directives from 2.2 will indeed cause issues when mixed > with Require (2.4). Do not mix them. Yes. Basically, they MUST NOT BE MIXED, but we should know how they behave when the mod_access_compat is loaded. I think it was like