Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of icebattle@gmail.com
 designates 209.85.146.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=ItvKp3KAgLJVIz6bTqr/PVQQE4fIS0u3rvnt+V9qBvWgO+N321nipOrgnO8deVec3eC4Q+mpVkPwPZEfgVaYnz/djFEVgbUZobVKIxjhPZcEtMUN8+WoHgGZrgENiO1B7Ebd0soAeAHWuy9V7LsRYFKJa8umrKWt29vilmZ0Xx0=
Message-ID: <ba8c99340708101309h1a911218tc50851f05ac599b6@mail.gmail.com>
Date: Fri, 10 Aug 2007 13:09:00 -0700
From: wi <icebattle@gmail.com>
To: users@httpd.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_23007_180713.1186776540027"
Subject: [users@httpd] mod_cache configuration issue

------=_Part_23007_180713.1186776540027
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all

We've made progress with our caching situation. However, we've discovered a
problem when caching for urls containing query strings.

When the url does not contain a query string, the object is cached as
expected, and the debug logging supports this. On the other hand, when the
url contains a querystring, it is not cached, and we get the following
logging:

 [debug] mod_cache.c(509): cache:
/users/123/games/360/headshot?test-token=testing not cached. Reason: Query
string present but no expires header

We aren't able to modify the backend server to provide an expires header, so
we tried to use the CacheIgnoreQueryString On option in the cache
configuration. Now we get the following error on startup:

Invalid command 'CacheIgnoreQueryString', perhaps misspelled or defined by a
module not included in the server configuration

This seems strange, since the server reports:

Server version: Apache/2.2.4 (Unix)
Server built:   May  3 2007 13:07:14

Which, as I understand it, should support this configuration. mod_cache,
mem_cache and disk_cache were built as shared objects, so they don't show up
on the httpd -l, but they are present in the modules directory. I've found
google items on CacheIgnoreQueryString from January this year, so I imagine
it must be a standard part of the sources we built.

Any ideas?

Also, if anyone has any ideas about how to add an expires header (we don't
have mod_headers compiled into the server) I'd like to hear.

Thanks!
Wayne

-- 
2X7 -> %A-3+ -> %K-7+ -> %9-?+ -> %Q-8 -> ?9-?9+

------=_Part_23007_180713.1186776540027
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all<br><br>We&#39;ve made progress with our caching situation. However, we&#39;ve discovered a problem when caching for urls containing query strings.<br><br>When the url does not contain a query string, the object is cached as expected, and the debug logging supports this. On the other hand, when the url contains a querystring, it is not cached, and we get the following logging:
<br><br>&nbsp;[debug] mod_cache.c(509): cache: /users/123/games/360/headshot?test-token=testing not cached. Reason: Query string present but no expires header<br clear="all"><br>We aren&#39;t able to modify the backend server to provide an expires header, so we tried to use the CacheIgnoreQueryString On option in the cache configuration. Now we get the following error on startup:
<br><br>Invalid command &#39;CacheIgnoreQueryString&#39;, perhaps misspelled or defined by a module not included in the server configuration<br><br>This seems strange, since the server reports:<br><br>Server version: Apache/2.2.4 (Unix)
<br>Server built:&nbsp;&nbsp; May&nbsp; 3 2007 13:07:14<br><br>Which, as I understand it, should support this configuration. mod_cache, mem_cache and disk_cache were built as shared objects, so they don&#39;t show up on the httpd -l, but they are present in the modules directory. I&#39;ve found google items on CacheIgnoreQueryString from January this year, so I imagine it must be a standard part of the sources we built.
<br><br>Any ideas?<br><br>Also, if anyone has any ideas about how to add an expires header (we don&#39;t have mod_headers compiled into the server) I&#39;d like to hear.<br><br>Thanks!<br>Wayne<br><br>-- <br>2X7 -&gt; %A-3+ -&gt; %K-7+ -&gt; %9-?+ -&gt; %Q-8 -&gt; ?9-?9+

------=_Part_23007_180713.1186776540027--