What happens with that request... The one that doesn't match your word list?
I would imagine it'll match another service directive. Might it not make sense to have one that *does* match your word list appear first in the config, and then use your redirect service after that? (which then doesn't have to worry about not matching a list) Joe > -----Original Message----- > From: Andreas Hilboll [mailto:[email protected]] > Sent: Monday, February 03, 2014 1:43 PM > To: [email protected] > Subject: [Pound Mailing List] URL pattern to negate a list > > Hi, > > I'd like to set up a service with a URL pattern matching only if the > path does *not* start with one of a list of words. > > The following doesn't work: > > Service > HeadRequire "Host: .*www.mydomain.com.*" > URL ! "^/project1|^/project2/|^/portal" > RedirectAppend "https://www.mydomain.com/portal"; > End > > > I also tried this pattern: > > URL "^(?!.*(?:project1|project2|portal)).*" > > but also it doesn't work. As you can see, I'm not good with regular > expressions in pound ... any help is greatly appreciated! > > Cheers, Andreas. > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. N�����r��zǧu�ޙ���+a���y�n�˛���m�h���u�l��!>W���(�֜��,z��+ ��+�笶*'
