Clik here to view.
Answer by Prathap Reddy for URL Fragment and 302 redirects
Posting similar issue with the solution faced by me.Hope it helps to someone with the similar requirement of preserving hash in IE for 302 redirects.Adding essential parts of the answer instead of...
View ArticleAnswer by Marcin for URL Fragment and 302 redirects
Just to let you know, here you can find proper spec. by w3c defining how all should behave: http://www.w3.org/TR/cuap#uri - clause 4.1 - see below:When a resource (URI1) has moved, an HTTP redirect can...
View ArticleAnswer by EricLaw for URL Fragment and 302 redirects
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...
View ArticleAnswer by ax. for URL Fragment and 302 redirects
Update 2022-09-22:RFC 9110/STD 97 HTTP Semantics (which obsoletes 7231 (and others)), has been published as an INTERNET STANDARD in June 2022. The wording in the newly numbered Section 10.2.2 Location...
View ArticleURL Fragment and 302 redirects
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...
View Article
