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 wrote:
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 authentication, the browser ending up at:
https://somesite.edu/reports/
...sans the named link reference. This is a problem in multiple browsers,
and I don't know if this is a bug in CAS, or a bug in our implementation of
CAS.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/35ebbc34-d73a-4e3a-b1ff-32b4d25816b3%40apereo.org.
