Scott: Could you ask the cas server directly for cas/service1 and then let CAS go to the actual service1 URL and cas filter? This way the "?service= " part could be removed from the original request. We used reverse proxy here to hide things, but the certificate work (HTTPS) gave us great issue. But I guess redirects would be seen anyhow in the browser unless somehow the request could come through the CAS URL is all cases. Somehow, be very light on CAS. And, why would it matter if the CAS server were the portal?
Are you trying to speed things or hide things more? David On 11/13/08, Scott Battaglia <[EMAIL PROTECTED]> wrote: > All, > > In the past we've had people request that CAS modify its matching > behaviors for service ids (i.e. to not include the query string or not > include the personally identifying item). I'm evaluating the best way > to do this in CAS4. One way to use Regular Expression patterns. Find > the part of the service id that matches the pattern and extract it and > then call equals on both of the pattern-extracted ids. > > Thoughts? > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > _______________________________________________ > cas-dev mailing list > cas-dev@tp.its.yale.edu > http://tp.its.yale.edu/mailman/listinfo/cas-dev > _______________________________________________ cas-dev mailing list cas-dev@tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas-dev
