Pattern Matching Problem

[Scott Battaglia]

We have an open issue related to adding priorities to the services
management tool (though in a general, a "most specific matches" might be the
best bet).    So its something that's on our agenda.

-Scott

On Fri, Mar 21, 2008 at 2:17 PM, oakridge <cerebro70 at yahoo.com> wrote:

>
> Hi all,
>
> I am trying to match two services that have similar paths.  Unfortunately,
> I
> have had little luck.  I am want to map requests to the Tomcat context of
> "/standard/*" to one service URL and "/standard/kiosk/*" to another.  This
> would allow me to have different login screens by using the theme support.
> Unfortunately the following mappings don't work:
>
> https://*/standard/*
>
> https://*/standard/kiosk/**
>
> Generally, the first pattern overrides the second for some reason (since *
> doesn't indicate multiple directories according to ant syntax).  Also,
> when
> I put in the URLs that I am explicitly requesting, neither pattern works
> (e.g. "https://www.mydomain.com/standard/kiosk/home_page.dispatch" and
> "https://www.mydomain.com/standard/home_page.dispatch").  Any help is
> appreciated.
> --
> View this message in context:
> http://www.nabble.com/Pattern-Matching-Problem-tp16204415p16204415.html
> Sent from the CAS Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>



-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080321/0fced715/attachment.html