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:31 AM, Lehman, Jason <[email protected]> wrote: > I wanted to bump this up. > > > > *From:* Lehman, Jason > *Sent:* Wednesday, November 13, 2013 10:19 AM > *To:* '[email protected]' > *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 > 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 also attached. > > > > Is there anything else I should turn on in the web.config CAS Client Log > config section to see where the issue might be? My server guys say there is > nothing on the server that is causing the redirect and when I switch the > serverName attribute in the web.config from https to http than everything > works fine. > > > > Thanks. > > > > > > Jason Lehman > > Applications Developer > > Web Services, University of South Florida > > [email protected] > > 813-974-7066 > > > > -- > 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-dev > > -- 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-dev
