On Mon, Sep 6, 2010 at 11:42 AM, Thom Brown <thom@xxxxxxxxx> wrote: > On 6 September 2010 16:10, Eric Covener <covener@xxxxxxxxx> wrote: >> On Mon, Sep 6, 2010 at 10:55 AM, Thom Brown <thom@xxxxxxxxx> wrote: >>> On 6 September 2010 12:49, Eric Covener <covener@xxxxxxxxx> wrote: >>>> Is the response cacheable? >>>> >>>> http://httpd.apache.org/docs/current/caching.html >>> >>> Just checked and it appears the header was returning no-cache in >>> Cache-Control. Using CacheIgnoreNoLastMod now. It meets all other >>> criteria. >>> >>>>>> MCacheMaxStreamingBuffer 300000 >>>> >>>> Is it larger than 300KB? >>> >>> I left it at 300KB because I didn't want a huge latency. As it's a >>> stream, it'll be indefinitately long. Have I misunderstood this >>> setting? >> >> I think so, as soon as the cache has seen 300KB of the response (over >> multiple chunks), it will decide the response on the whole is too big >> to be cached. > > By that logic, streams can't really be cached using mem_cache as it > will always hit the limit. Do I need to look at something else, like > Varnish? If you define a stream as an infinitely long response, then I don't think it can be stored in memory. -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|