o.github.io/cas/5.1.x/installation/User-Interface-Customization-CSSJS.html#preserving-anchor-fragments
>
> --Misagh
>
> - Original Message -
> From: "Andrew Morgan" <mor...@orst.edu>
> To: "CAS Community" <cas-user@apereo.org>
> Sent: Tue
org>
Sent: Tuesday, August 22, 2017 9:28:04 AM
Subject: Re: [cas-user] CAS drops named anchors
Fragments (named anchors) are not sent to the server. Search your web
server access logs - you won't see a "#" in them. :)
You can read a bit about it here:
http://codetunnel.i
Fragments (named anchors) are not sent to the server. Search your web
server access logs - you won't see a "#" in them. :)
You can read a bit about it here:
http://codetunnel.io/how-to-persist-url-hash-fragments-across-a-login-redirect/
Andy
On Mon, 21 Aug 2017, Dusty Edenfield
Is there any solution for when CAS drops named anchors upon login redirect?
Example:
It appears (from LiveHTTPHeaders and HTTPFox traces) that CAS is dropping
named anchors from target URLs. For example, going to the CAS-protected URL:
https://somesite.edu/reports/#Mobile
results, after
