On Thu, Jul 16, 2009 at 12:00 PM, Javier Guerra <jav...@guerrag.com> wrote:
> > On Thu, Jul 16, 2009 at 3:51 PM, Michael<newmani...@gmail.com> 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 attribute? i imagine three > answers: > > 1: no #section1 in the HTML => Django is losing it, should be fixed > > 2: #section1 present, but not urlencoded => Django should encode it, > since it's a parameter for the view wrapper. > > 3: #section1 present and urlencoded => browser's fault, should be > worked around with JavaScript > The fragment identifier is not transmitted to the server from the browser: Request headers for http://www.djangoproject.com/#test GET / HTTP/1.1 Host: www.djangoproject.com User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Pragma: no-cache Cache-Control: no-cache Check your server logs if you don't believe me. The browser carries the fragment identifier through redirects, so if it is passed through the form's post it will appear in the last redirect with the JS I mentioned earlier. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
