On Feb 15, 2009, at 3:28 PM, Malcolm Tredinnick wrote:
> > On Sun, 2009-02-15 at 08:30 -0800, mermer wrote: >> OK - I've found the problem. I'm using Firefox (Version 3.06) but >> the >> problem is actually with Firebug, which I've been using to view the >> headers. >> >> With Firebug disabled, it works fine (viewing the headers through >> another app). > > Realise that a browser isn't *required* to send if-none-match. So this > isn't really a bug in Firebug. It's possibly deliberately not sending > the header to ensure that it sees the full interaction each time, > rather > than a 304 response. > > Also, you probably want to make sure you're also handling > if-modified-since, as that's also used to check for "liveness". > > Regards, > Malcolm No sorry, this is definitely a Firebug bug. http://code.google.com/p/fbug/issues/detail?id=1274 Ric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
