https://issues.apache.org/bugzilla/show_bug.cgi?id=50317
--- Comment #16 from Jim Riggs <[email protected]> --- (In reply to Jim Riggs from comment #15) > I don't understand why you are seeing different results. I just ran a test > with your configuration (except I set max-age=10). I then ran `ab -k -c 2 -t > 30' (30-second test), and only 3 requests went to the backend as expected. And that was 50,000 requests. 3 went to the backend. I do notice, however, that when we serve stale content we are not setting an Age header. It seems that RFC2616[1][2] requires this for 1.1: "An HTTP/1.1 server that includes a cache MUST include an Age header field in every response generated from its own cache." So should we setting an Age header "in every response", even when we are serving stale cache? If so, what value do we use for the age? The real (now expired) age? Does anyone know what real-world affect that would have downstream? [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.6 [2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.3 -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
