returning to #<location> is getting stripped.

[Jim Fox]

You can solve similar problems with javascript.  For example,
to refresh a session you can set the fragment in a cookie,
send the user through login, and recover the fragment on
their return.

Jim


On Thu, 14 Aug 2014, Cantor, Scott wrote:

> Date: Thu, 14 Aug 2014 06:37:46
> From: "Cantor, Scott" <cantor.2 at osu.edu>
> To: Shib Users <users at shibboleth.net>
> Reply-To: Shib Users <users at shibboleth.net>
> Subject: Re: returning to #<location> is getting stripped.
> 
> On 8/14/14, 8:31 AM, "Nickles, Brent" <bnick001 at umaryland.edu> wrote:
>
>> I¹m not sure if this is an SP/IdP issue or something else.    Any help is
>> appreciated.
>>
>> I¹m noticing that if I try to access a URL like this:
>> https://xxx.xx.xxx/mypage.html#location
>> after a successful authN, it seems to lose the #location part of t
>> he URL. Do you know if there¹s any way to fix that?
>
> No, because that fragment is not part of the URL. It's not sent to the
> server, so there's no way for it to reappear. Fragments are a client side
> thing. If a browser accesses a link with a fragment, it requests the URL
> minus the fragment, and then applies the fragment locally.
>
> -- Scott
>
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>