: Re: [cas-dev] SSL and CAS .NET Client
We had an issue a while back where links were generated incorrectly when using
nonstandard https ports, but it was resolved shortly after being identified.
There could be a reverse proxy or SSL offloader re-writing links & headers
that's c
We had an issue a while back where links were generated incorrectly when
using nonstandard https ports, but it was resolved shortly after being
identified. There could be a reverse proxy or SSL offloader re-writing
links & headers that's configured incorrectly.
-Scott
On Mon, Nov 18, 2013 at 11:
I wanted to bump this up.
From: Lehman, Jason
Sent: Wednesday, November 13, 2013 10:19 AM
To: 'cas-dev@lists.jasig.org'
Subject: SSL and CAS .NET Client
With the CAS .NET client we are having an issue where we are not being directed
back to https://servername but instead being directed back to
With the CAS .NET client we are having an issue where we are not being directed
back to https://servername but instead being directed back to
http://servername:443. I have attached the Live HTTP Headers log for a session
where this occurred. No CAS Client log gets written. The web.config is als
