I was wondering whether this current behavior with respect to http redirects
on fragmented urls is actually a desired behavior, or some bug.
Let's suppose the user issues a GET request to the URI '/action#home'.
Now, the handler which is associated with this, processes the request and
lets suppose it wants to issue a http 302 to fetch the url '/' without any
specific fragment, in response.
Currently, this scenario seems to be not achievable in django using a simple
HttpResponseRedirect('/'), as the fragment from the last requested GET is
automatically appended to the next fetch request at the client side, which
results from the 302 response issued.
So, instead of being redirected to '/' the user experiences a redirect to
'/#home', which might not be what was intended at the first place.
Issuing a 302 response with a specified fragment identifier does not have
the problem. But, the thing is, what if we want to redirect to a url without
specifying any primary fragment.
So, my query basically come down to: Is this behavior expected, or not
expected?
Or, is it the client browser whose current implementation of 302 response,
the only cause for this?
--
Thanks,
Subhranath Chunder.
www.subhranath.com
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
