URI fragment must be inherited by the redirect location

[NiteshKant]

For 3xx redirects, according to spec: http://tools.ietf.org/html/rfc7231#section-7.1.2 the redirect URI must carry forward the URI fragment from the original request if not provided in the redirect location.

[NiteshKant]

Now, the redirect URI inherits the fragment if none present. The behavior follows as described in this example in the spec:

For example, a GET request generated for the URI reference
   "http://www.example.org/~tim" might result in a 303 (See Other)
   response containing the header field:

     Location: /People.html#tim

   which suggests that the user agent redirect to
   "http://www.example.org/People.html#tim"

   Likewise, a GET request generated for the URI reference
   "http://www.example.org/index.html#larry" might result in a 301
   (Moved Permanently) response containing the header field:

     Location: http://www.example.net/index.html

   which suggests that the user agent redirect to
   "http://www.example.net/index.html#larry", preserving the original
   fragment identifier.