I am testing the CacheFilter with the following parameter:

<init-param>
        <param-name>max-age</param-name>
        <param-value>no init</param-value>
    </init-param>

It seems to properly omit the max-age cache control header on the first page request (when the content is initially built), but on subsequent requests (when the content is served from cache) the max-age header is set to 60.

Here are the request and response headers from my test case, two requests for the same page, two seconds apart:

******* FIRST REQUEST ********
GET /proxy_cache_test.jsp?h=1 HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Host: current.us.localhost:8080
Connection: Keep-Alive

******* FIRST RESPONSE ********
HTTP/1.1 200 OK
Server: Resin/3.0.22
X-Wescom-Server: WSIN070
Content-Type: text/html
Transfer-Encoding: chunked
Date: Tue, 13 Feb 2007 16:13:36 GMT

******* SECOND REQUEST ********
GET /proxy_cache_test.jsp?h=1 HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Host: current.us.localhost:8080
Connection: Keep-Alive

******* SECOND RESPONSE ********
HTTP/1.1 200 OK
Server: Resin/3.0.22
X-Wescom-Server: WSIN070
Cache-Control: max-age=60
Content-Type: text/html
Content-Length: 862
Date: Tue, 13 Feb 2007 16:13:38 GMT

This appears to be a bug.