Re: HTTP Response Code 304

Are you positively shure the pages are not cached in any downstream
caches like the browsers cache?

304 responses does not and cannot carry any content. This is by
definition of status code 304 in the HTTP protocol. It is a very
specific status code with very specific exceptions in the protocol
format (no content transmitted, even if the headers seems to indicate
there is)

--
Henrik Nordstrom
Squid hacker
Adi Linden wrote:
> 
> I have a webserver which returns all pages with response code 304. All
> pages send from the server come up with TCP_MISS/304 and are not cached.
> The content still makes it to the browser, though.
> 
> Adi
> 
> On Sat, 10 Jun 2000, Henrik Nordstrom wrote:
> 
> > Adi Linden wrote:
> >
> > > Why aren't pages with the HTTP response code 304 cached? I am running an
> > > apache webserver with all static pages and vhosts. All of the pages come
> > > back with response 304 and none get cached. The problem is this is one of
> > > the sites the cache is intended for.
> >
> > Because 304 replies are not pages, it is only a notice telling a cache
> > that the page has not been modified.
> >
> > > The store log shows which pages make it to the disk cache. Is there any
> > > way to determine why pages aren't cached, i.e. make the store log more
> > > verbose?
> >
> > store.log has this information already. It is RELEASE requests with the
> > filenumber FFFFFFFF
> >
> > --
> > Henrik Nordstrom
> > Squid hacker
> >