Re: [Query] http redirect to non-fragmented url coming from fragmented url

2011-08-25 Thread Tom Evans
On Thu, Aug 25, 2011 at 5:58 PM, Subhranath Chunder wrote: > I got the idea of what was happening looking at the behavior pattern itself. > But, what I was not sure whether these behaviors were defined or just > working like that. Which might lead to some other

Re: [Query] http redirect to non-fragmented url coming from fragmented url

2011-08-25 Thread Subhranath Chunder
I got the idea of what was happening looking at the behavior pattern itself. But, what I was not sure whether these behaviors were defined or just working like that. Which might lead to some other inconsistencies. As, in my case the fragment was coming from some other third-party source. Facebook

Re: [Query] http redirect to non-fragmented url coming from fragmented url

2011-08-25 Thread Tom Evans
On Thu, Aug 25, 2011 at 4:04 PM, Subhranath Chunder wrote: > Yes, I do understand that fragment identifiers are not sent to the server. > But, I was not talking about that. > Infact, I was talking about the fragments send in the response as http 302 > response specifically.

Re: [Query] http redirect to non-fragmented url coming from fragmented url

2011-08-25 Thread Subhranath Chunder
Yes, I do understand that fragment identifiers are not sent to the server. But, I was not talking about that. Infact, I was talking about the fragments send in the response as http 302 response specifically. Maybe, I'll put a little code snippet below to explain the case better: :) urls.py =

Re: [Query] http redirect to non-fragmented url coming from fragmented url

2011-08-25 Thread Tom Evans
On Thu, Aug 25, 2011 at 12:48 PM, Subhranath Chunder 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

[Query] http redirect to non-fragmented url coming from fragmented url

2011-08-25 Thread Subhranath Chunder
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