On this subject, see
https://github.com/apereo/cas/commit/1d9b5bad50493d6bca62f8e0ca38ca21c66199aa#r116140207
(*) where I explain two possibilities:
* hash not encoded in service :
https://cas/login?service=http://localhost/#foo=bar
It happens when user browses http://localhost/#foo=bar and the server-side
application redirects to CAS.
The browser is propagating the hash param (typical browser behavior in case of
HTTP 302).
* hash encoded in service :
https://cas/login?service=http://localhost/%23foo=bar
It happens when the redirect to CAS is browser initiated in javascript,
or when the server-side application forces a hash param
=> nothing to do in browser. location.hash is always empty
(*) here we have CAS >= 6.6.8 but we reverted the modification to have behaviour
of CAS < 6.6.8
- action += location.search + encodeURIComponent(location.hash);
+ action += location.search + location.hash;
On 11/01/2024 08:43, Benny Lu wrote:
Hello:
As shown in the pic
The original url is
http://localhost:8881/login?service=http://localhost:9280/cas/login?ddtab=true%26target%3Dhttp%3A%2F%2Flocalhost%3A9999%2F%23%2Findex
<http://localhost:8881/login?service=http://localhost:9280/cas/login?ddtab=true%26target%3Dhttp%3A%2F%2Flocalhost%3A9999%2F%23%2Findex>
but when the url got redirected the special characters disappears
I wonder when the special characters disappears and how can i keep the
characters remain in my target url
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
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/ab4ad198-120d-40cb-bbbc-e7f929969519%40univ-paris1.fr.
