Re: [users@httpd] Regex fails to complie

Just to close this out, m#regex# worked perfectly, thanks for the tip. On Thu, Aug 25, 2016 at 4:27 PM, Eric Covener wrote: > On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis > wrote: > > > > The limitation is that you cannot use the separator inside the

Re: [users@httpd] Regex fails to complie

I will investigate that. On Thu, Aug 25, 2016 at 4:48 PM, Daniel wrote: > Why not just use the directive "UseCanonicalName on"? > > El 25/8/2016 10:27 p. m., "Eric Covener" escribió: > >> On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis

Re: [users@httpd] Regex fails to complie

I'm not sure if that will working when using Apache for a forward proxy. I only want to allow proxied request to *.foo.com. where foo.com is the domain of the target of the request, not the domain of the apache server. On Thu, Aug 25, 2016 at 4:48 PM, Daniel wrote: > Why

Re: [users@httpd] Regex fails to complie

Why not just use the directive "UseCanonicalName on"? El 25/8/2016 10:27 p. m., "Eric Covener" escribió: > On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis > wrote: > > > > The limitation is that you cannot use the separator inside the regex, > even

Re: [users@httpd] Regex fails to complie

On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis wrote: > The limitation is that you cannot use the separator inside the regex, even when you escape it. It's a limitation in the expression engine used for If, not the regex library. You can use m#...# in your case. --

[users@httpd] Regex fails to complie

Hello, I'm trying to reject requests hitting my apache proxy which are NOT going to *.foo.com, *.foo.com:443 or *.foo.com/blahblahblah. I'm trying to avoid bogus requests like foo.com.baddomain.com. The regex I'm using is: \.foo.com(?:\:\d{2,5}|\/.*)?$ This is working exactly how I want on