mod_proxy/4229: Cache directory not initialised

[Graham Leggett <gr...@vwv.com>]

>Number:         4229
>Category:       mod_proxy
>Synopsis:       Cache directory not initialised
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Apr 12 08:50:01 PDT 1999
>Last-Modified:
>Originator:     graham@vwv.com
>Organization:
apache
>Release:        v1.3.6
>Environment:
SunOS infobase2 5.7 Generic sun4u sparc SUNW,Ultra-250
gcc v2.8.1
>Description:
When setting Apache up as a reverse proxy using the "ProxyPass" and
"ProxyPassReverse" directives, Apache refuses to cache any data going
through it. The CacheRoot directory is configured, and is writable by the
Apache user, however this directory remains empty. No error messages appear
in any log file reporting the failure of writing of objects to the cache but...

The failure to write to the cache triggers bug PR3178, it seems the filename
of the file the object is being cached under is a NULL string.
>How-To-Repeat:
Set up Apache install as a reverse proxy for a website, try enable caching.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]