Re: [Pound Mailing List] Defining multiple URL patterns in a Service

On Fre, 2013-05-03 at 12:47 +0100, Conor McCarthy wrote:
> On 29 April 2013 15:57, Joe Gooch <[email protected]> wrote:
> 
> > The documentation says you can have multiple directives… It doesn’t
> > indicate whether they’re and-ed or or-ed together.  (The fact that it calls
> > them conditions leads me to believe they’re restrictive)  I also agree the
> > code appears to be doing an And relation.****
> >
> > ** **
> >
> > Personally it’s never occurred to me to try to use multiple URL directives.
> > ****
> >
> > ** **
> >
> > I agree in your case Or is what you want.  I’m having a hard time thinking
> > of a reason you might want to use Ands…  Maybe some sort of exclusionary
> > rule using negative lookaheads.. but with regular expressions I would think
> > you could do that on one line as well.****
> >
> > ** **
> >
> > “Or” logic committed to stage_for_upstream/v2.7b
> >
> 
> Excellent, thanks!
> 
> The specific use case is sets of URLs which require different Backend
> (and possibly Session) settings, so it's simplest to have  a config like:
> 
> ListenHTTP
> 
>     Address 10.1.2.3
>     ....
> 
>     ## special URLs
>     Service
>         URL "^/url1"
>         URL "^/url2"
>         URL ....
> 
>         Backend
>             ...
>         End
>     End
> 
>     ## default
>     Service
>         ...
>     End
> End
> 
> After a while a single URL regex with multiple grouped alternatives becomes
> troublesome and error prone.
> 
> Regards,
>  Conor.

There is a reason for it: it is easy to write an OR regular expression,
but AND expressions can be more difficult.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19


--
To unsubscribe send an email with subject unsubscribe to [email protected]
Please contact [email protected] for questions.