Re: etag and 404.

2007-04-18 Thread Atilla
I stand corrected, thank you for the referenced reply. I've missed that part of the specification. If you make any changes to the conditional get middleware, please consider sending a patch for it, that could be incorporated in the code later, hopefully. --~--~-~--~~~-

Re: etag and 404.

2007-04-17 Thread eliott
reply to myself... I just discovered the bug on the tracker for this... http://code.djangoproject.com/ticket/3206 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send emai

Re: etag and 404.

2007-04-17 Thread eliott
After some research, it does appear to be non RFC compliant behavior. I get this behavior when running django via the "python manage.py runserver" command. The client, in this case firefox, upon recieving an etag on a 404 response, will subsequently send an If-None-Match header for the next reques

Re: etag and 404.

2007-04-17 Thread Atilla
On 16/04/07, cactus <[EMAIL PROTECTED]> wrote: > > > I think the behaviour is correct though, why do you want to redefine it ? > > If the behavior is indeed correct, then I don't think I need to > redefine it. > It just seemed odd to return a 'not-modified' response to a query for > a page that di

Re: etag and 404.

2007-04-16 Thread cactus
> I think the behaviour is correct though, why do you want to redefine it ? If the behavior is indeed correct, then I don't think I need to redefine it. It just seemed odd to return a 'not-modified' response to a query for a page that did not exist. Apache, when configured with mod_expires, does

Re: etag and 404.

2007-04-16 Thread Atilla
> When I enable etags, django is sending back an etag on 404 pages. > When a client does a subsequent request for the same nonexistent > page, a 304 response is sent back, because the page has not changed > (based on the etag). > > When I disable etags, multiple requests for a non existent page a

etag and 404.

2007-04-15 Thread cactus
When I enable etags, django is sending back an etag on 404 pages. When a client does a subsequent request for the same nonexistent page, a 304 response is sent back, because the page has not changed (based on the etag). When I disable etags, multiple requests for a non existent page all return 4