Hi, I have an shtml page with the following code: <HTML> Before bla bla bla <!--#include virtual="/cj/cached/nocambia.shtml" --> After bla bla bla </HTML> I use mod_proxy and mod_cache with mod_disk_cache. When the page is retreived from the first time, I can see the output ok. On the browser you receive something like this: <HTML> Before bla bla bla included page After bla bla </HTML> The next time, if the page hasn´t expired, mod_cache gets the page from the cache and serve's the resource, but then the rest of the document is "lost". The client never receives anything from the inclide statement to the end of the document. On the browser you receive something like this: <HTML> Before bla bla bla included page I tried with several version's of apache without success. My httpd.conf is: Options +Includes Listen 8080 AddType text/html .shtml AddOutputFilter INCLUDES .shtml <VirtualHost *:8080> ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> SetOutputFilter INCLUDES CacheRoot /home/apache/apache_2.2.3/cache/ CacheEnable disk /cj/cached CacheMaxFileSize 100000 CacheMinFileSize 1 CacheDirLevels 2 CacheDirLength 1 CacheMaxExpire 60 ProxyPass /cj http://192.168.203.131:7001/cj ProxyPassReverse /cj http://192.168.203.131:7001/cj ErrorLog /home/apache/apache_2.2.3/logs/vhost_8080_error.log CustomLog /home/apache/apache_2.2.3/logs/vhost_8080_access.log common </VirtualHost> I set the following HTTP headers in the cached files: Last-modified, Expires and Cache Control (with max-age an s-maxage) I've read thousands of pages and didn´t find anything. Is this a bug? or a misconfiguration?
I am sorry, but I cannot reproduce this with trunk. Which revsion are you using? Or are you using one of the stable releases of 2.0.x or 2.2.x?
(In reply to comment #1) > I am sorry, but I cannot reproduce this with trunk. Which revsion are you using? > Or are you using one of the stable releases of 2.0.x or 2.2.x? Hi! Thanks for your response. I test this case with apache 2.0.59 stable and 2.2.3 stable too. Both of them in a debian machine: Linux debian01 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux How can I help you to reproduce this issue?
Is this problem still there with 2.2.4?