...
Code Block |
---|
CONFIG proxy.config.http.background_fill_completed_threshold FLOAT 1.000000 |
HTTP Cache
...
Options
The following These two settings are pretty important. I'll go through them one at a time.
This one One defines a global variable whose function is to indicate
whether specific HTTP headers
are necessary to properly cache an object. As it turns out, much of this
functionality is
included in HTTP 1.1 and thus additional headers aren't really necessary.
Code Block |
---|
CONFIG proxy.config.http.cache.required_headers INT 0
|
The next The other specifies how "stale" an object should be before it gets fetched again from the Internet.
The default config for ATS specifies that after 1 week(604800 seconds), any object that is "stale"
should be flushed from the cache. I'd prefer that it stick around for about 3 months.
Code Block |
---|
CONFIG proxy.config.http.cache.required_headers INT 0
CONFIG proxy.config.http.cache.max_stale_age INT 7776000
|
Cache Object Byte Serving
While the following option This one specifies whether or not to use HTTP "range" requests. While having this option enabled
will save bandwidth, it also reduces the speed of webpages loading.
I decided to disable itslows page loading.
Code Block |
---|
CONFIG proxy.config.http.cache.range.lookup INT 0 |
...
The default config for ATS specifies that after 1 day(86,400 seconds), any object without a specific expiration
should be flushed from the cache. I'd prefer that it stick around for about 3 months. This setting is contentious
in that what it should be is debatable.
...