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. Mark -- "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
-- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
