> The only way I know around this involves leaning on JavaScript to
> get the URL, split off the #hash bit from it, and sneak it in as
> a hidden element on the login form.
Yeah, I ended up doing this on the /login page. Basically:
$(function() {
$('#url-hash').attr('va
> The first problem is that the django server only receives the '/page'
> part of the URL. The browser itself holds onto the '#hash' part and
> doesn't transmit that to the django server at all, so the
> login_required() decorator calls request.get_full_path() and gets '/
> page', so that's what
On Thu, Jul 16, 2009 at 4:08 PM, Tom Evans wrote:
>> 1: no #section1 in the HTML => Django is losing it, should be fixed
>
> Re-read the thread. The #part of the URL is not something ever
> transmitted beyond the browser. No web application ever sees the #part
> of a URI.
as i understand it, the
On Thu, Jul 16, 2009 at 12:00 PM, Javier Guerra wrote:
>
> On Thu, Jul 16, 2009 at 3:51 PM, Michael wrote:
> > This information isn't transmitted to the server in anyway so short of
> what
> > you described above, Django can't really solve your issue.
>
> but where is it getting lost? i mean, wh
On Thu, 2009-07-16 at 16:00 +, Javier Guerra wrote:
> On Thu, Jul 16, 2009 at 3:51 PM, Michael wrote:
> > This information isn't transmitted to the server in anyway so short of what
> > you described above, Django can't really solve your issue.
>
> but where is it getting lost? i mean, what
On Thu, Jul 16, 2009 at 3:51 PM, Michael wrote:
> This information isn't transmitted to the server in anyway so short of what
> you described above, Django can't really solve your issue.
but where is it getting lost? i mean, what does the html looks like?
does it have the #section1 in the action
On Thu, Jul 16, 2009 at 11:18 AM, Jumpfroggy wrote:
>
> On Jul 16, 11:05 am, Javier Guerra wrote:
> > maybe urlencode()'ing the '/page#section1' parameter?
>
> The first problem is that the django server only receives the '/page'
> part of the URL. The browser itself holds onto the '#hash' part
On Jul 16, 11:05 am, Javier Guerra wrote:
> maybe urlencode()'ing the '/page#section1' parameter?
The first problem is that the django server only receives the '/page'
part of the URL. The browser itself holds onto the '#hash' part and
doesn't transmit that to the django server at all, so the
l
On Thu, Jul 16, 2009 at 2:58 PM, Jumpfroggy wrote:
>
> Currently, the @login_required() decorator does not preserve any #hash
> part of the URL. So if I go to /page#section1 without being logged
> in, I'm redirected to /login?next=/page#section1. After logging in,
> I'm redirected to /page (with
Currently, the @login_required() decorator does not preserve any #hash
part of the URL. So if I go to /page#section1 without being logged
in, I'm redirected to /login?next=/page#section1. After logging in,
I'm redirected to /page (without the hash part).
I read in another thread here that the h
10 matches
Mail list logo