Thanks Scott, I think I have worked out my problem situation is when I attempt to access my webapp using something like the following (the webapp is available on HTTPS and HTTP):
https://localhost:8443/webapp But in my web.xml my serverName parameter is set to "localhost:8080", after CAS login, this resulted in trying to redirect me to: https://localhost:8080/webapp Which is clearly wrong, if there was an optional way for me to make the scheme an explicit parameter, I think this would be a good feature. Mark On 3/20/07, Scott Battaglia <[EMAIL PROTECTED]> wrote: > Mark, > > It should be grabbing the https/http based on whether the URL accessed is > secure or not (i.e. request.isSecure()). > > -Scott > > > On 3/20/07, Mark McLaren <[EMAIL PROTECTED]> wrote: > > > > I am a regular user of the version 2 CAS Filter although I guess this > > query could equally apply to version 3 also. > > > > I regularly use non-standard server HTTPS ports (e.g. Tomcat default > > port of 8443). I am not sure if this is absolutely necessary but can > > a parameter be added to the CAS authentication filter to specify when > > a client server is using HTTPS? (or not) > > > > As I understand it, the serverName parameter does not specify > > HTTP/HTTPS (e.g. localhost:8443). I can specify a protocol scheme by > > using the serviceUrl (e.g. > https://localhost:8443/webapp/login.jsp) > > but this implies a slightly different behaviour, a single point of > > application entry, and this is not always what I want. -- "Paradoxically, the more time saving abstractions you are using the more you actually have to know." - Simon Willison _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
