Is the URL fragment and 302 redirects automatically removed?
Since redirect hidden variable value contains only /myapp/ without hash fragment and it’s a 302 redirect, the hash fragment is automatically removed by IE even before coming to our application and whatever the solutions we are trying in our application code are not working out.
Is the URL fragment sent to the server?
It’s well known that the URL fragment (the part after the #) is not sent to the server. I do wonder though how fragments work when a server redirect (via HTTP status 302 and Location: header) is involved.
When does an HTTP Redirect indicate a resource has moved?
When a resource (URI1) has moved, an HTTP redirect can indicate its new location (URI2). If URI1 has a fragment identifier #frag, then the new target that the user agent should be trying to reach would be URI2#frag. If URI2 already has a fragment identifier, then #frag must not be appended and the new target is URI2.
How to define an URL path segment string?
A URL-path-segment string must be one of the following: 1 zero or more URL units excluding U+002F (/) and U+003F (?), that together are not a single-dot path segment or a double-dot path segment. 2 a single-dot path segment 3 a double-dot path segment.
Why does a redirect lose its hash fragment?
The only problem here is that the redirect URL has lost its hash fragment because the URL the login form POSTed to didn’t have a hash fragment for the browser to persist like it did when we refreshed the page we were on that already had a hash fragment.
When to drop url fragment in Safari 5?
Safari 5 and IE9 and below drop the original URI’s fragment if a HTTP/3xx redirect occurs. If the Location header on the response specifies a fragment, it is used. IE10+, Chrome 11+, Firefox 4+, and Opera will all “reattach” the original URI’s fragment after following a 3xx redirection.