Tomcat 7.0.26 lives on the same server and is hosting the CAS webapp. It is currently using the default ports 8080 for regular traffic and 8443 for SSL traffic.
Curl Results: ---------------- For == > https://my_server.highline.edu:8443/cas/login SSL negotiated successfully and certificate verified, followed by HTML for the login page For ==> https://my_server.highline.edu:8443/cas/services/j_acegi_cas_security_check?ticker=<some service ticket id> SSL negotiated successfully and certificate verified, followed by 500 internal server error, followed by HTML for "CAS is unavailable" page For ==> https://my_server.highline.edu:8443/cas/services SSL negotiated successfully and certificate verified, followed by 302 Moved temporarily to redirect the login page Here is the 500 internal server error part of the output. =========--------------------------------------=========== > < HTTP/1.1 500 Internal Server Error < Server: Apache-Coyote/1.1 < Cache-Control: private < Expires: Wed, 31 Dec 1969 16:00:00 PST < Set-Cookie: JSESSIONID=C74165BBA42E43EA8C776D734CBB3997; Path=/cas/; Secure; HttpOnly < Content-Type: text/html;charset=UTF-8 < Transfer-Encoding: chunked < Date: Mon, 21 Oct 2013 21:05:50 GMT < Connection: close < <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> <!-- more html follows --> =========--------------------------------------=========== Using netstat I can see that the problem may lie in the the web client portion: root@my_server:/# netstat -sp tcp | grep connection 2029 active connections openings 1175 passive connection openings 1 failed connection attempts 423 connection resets received 7 connections established 208 connections reset due to unexpected data 228 connections reset due to early user close 4 connections aborted due to timeout Notice the connections reset due to early user close Now I access the page again and rerun the command. root@my_server:/# netstat -sp tcp | grep connection 2031 active connections openings 1181 passive connection openings 1 failed connection attempts 427 connection resets received 9 connections established 208 connections reset due to unexpected data 230 connections reset due to early user close 4 connections aborted due to timeout Notice the connections reset due to early user close went up by two. Just like the log file shows two connection reset exceptions for each attempt. -- <BR> You are currently subscribed to [email protected] as: [email protected] <BR> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
