| this problem has me stumped.. and i have no idea why this is happening. i have a function which calculates a context variable based on the request.path in this example, base is hard-coded to "popular/" and the request.path is "/aggy/popular/" I then calculate basepath ala basepath = request.path[:request.path.rfind(base)] now.. looking at this I expect basepath to be "/aggy/" and for *most* requests it's working. *BUT* for some reason every once and a while it thinks basepath is another completly different (but valid) URL eg /aggy/tag/play/ which I'm guessing is someone else's request. if you try http://vc-chat.com/aggy/popular/d/7/ with 2 browsers open (and refresh a couple of times) you will see it as well check the links after See Popular posts over the last --- I've also seen similar things when I create several new objects in a row. after the first/second one it seems to fill the '{{object}}' variable with the previous' requests results. anyone have any ideas? or seen similar things? it looks like something is corrupted.. regards Ian -- Ian Holsman http://zyons.com/ build a Community with Django --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~--- |
- weird problem regarding crud coming into the request Ian Holsman
- Re: weird problem regarding crud coming into the r... Malcolm Tredinnick
- Re: weird problem regarding crud coming into t... Ian Holsman
- Re: weird problem regarding crud coming in... Ian Holsman
