On Thu, Aug 25, 2011 at 12:48 PM, Subhranath Chunder
<[email protected]> wrote:
> 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'.
Stop. Browsers do not send fragment identifiers to a server, they are
solely used by the browser.
> 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.
Er - my browser doesn't do that. Are you sure you've tracked this through?
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
