I got a CAS4.0 server running in tomcat, behind an apache reverse-proxy. So, the end-users goes to someurl.com/cas (apache). Apache forwards this request on behalf of the user to someurl.com:8443/cas (tomcat, cas).
In tomcat, I have specified a proxyPort="443" argument for the http-connector 8443, so that all internal calls in cas returns 443. This instructs the tomcat api calls such as ServletRequest.getServerPort() to return 443, instead of the actual 8443. This is usually a good practice, because if cas were to use this value in a redirect or send it back to the end-user for some reason, the end-user would be lost, as only my apache-proxy gets through the 8443 port - I want the end clients to access cas through 443. This works wonderfully, with one exception. CAS it self works great behind the apache proxy and with the proxyPort for the connector set. But the CAS REST API doesen't work, when specifying a proxyPort in the tomcat connector. The restlet service is started, and I can access it, but I only get the restlet 404 page(not general tomcat 404) when doing a POST to cas/v1/tickets. If I remove the proxyPort="443" from the tomcat connector, the REST API works again. Is this a known problem? A configuration error on my part? or a likely bug? -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
