oggie rob wrote: > I'm a little concerned that you found this - I deployed a similar app > several months ago and have not heard of a single case of this. (I'm > using rev 1764.)
Actually, the only place I've discovered it is at my work place, and from here it does seem to be fixed with the changes in place. My first guess was that I'm behind some cache that adds headers or something that change the way my browser treats the page, but after looking at the headers I'm receiving I don't see any evidence of that. I'm am certainly behind a web proxy, but I don't know what it might be doing. A different possibility is that there is a proxy/cache somewhere caching pages itself - I haven't eliminated that yet (I assumed before that it was my browser caching it, mainly due to the fact that the page was returning instantly, but it might be a fast nearby cache doing the caching). I'm not sure if I can really spend any more of my company's time diagnosing this problem! Certainly the change has worked, and could be useful for anyone in a similar situation. Regards, Luke --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
