httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphaël <>
Subject Re: [users@httpd] AW: mod_cache/mod_cache_disk responses missing Content-Type header
Date Wed, 08 Jun 2016 17:19:23 GMT
On Mon, Dec 21, 2015 at 11:39:55AM -0500, Eric Covener wrote:
> On Mon, Dec 21, 2015 at 11:25 AM, Alexander Härtig
> <> wrote:
> > AH00717: Premature end of cache headers.
> The error reporting is very poor there. Are you able to patch
> mod_cache_disk and run with at least LogLevel debug?

trace8 brings nothing new w.r.t debug (as sent in my previous email)

I found the following behavior interesting :
GET /  => OK          # put in cache
POST / => OK          # invalidate cache
POST / => not OK      # cache_disk:error AH00717

My guess is that it comes from following patch from 2013:
> mod_cache: Invalidate cached entities in response to RFC2616 Section

* It seems it introduced a CACHE_INVALIDATE filter (for which, sadly, I
  didn't find much documentation)
* I guess it introduced an invalid code path triggering
  invalidate_entity() => recall_headers() for an already invalidated entity.

Maybe this error it just the symptom of trying to invalidate a "removed"
entity twice.

When doing tests I was also able to encouter easily:
> AH02468: cache: Attempted to invalidate cached entity with key: http://xxxx:80/index.php?
by just playing a bit with htcacheclean

(side note: htcacheclean -A <URL> is an incorrect usage, but an unexpected behavior)

Going further, I guess that the second invalidation shows this issue because
the first invalidation (in during the first POST) failed to output a
valid mod_cache file.

Attached the initial cache header file (GET.txt, just after a GET), copied from
and then just after a POST was issued (successive POSTs cause the error
but don't change this file anymore) : POST.txt

I hope it makes things clearer and could help bringing up a full
explanation + fix + workaround.

thank you

View raw message