According to the HTTP/1.1 RFC, "All HTTP date/time stamps MUST be
represented in Greenwich Mean Time (GMT), without exception."
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.3
I suspect that TS is having problems parsing the Date format to
calculate the Age.
--Steve
Pranav Modi wrote, on 8/9/10 12:04 AM:
On checking again, the time sent from TS does not change - remains
constant at 01:54:01 EDT. What could be the problem here?
Thanks,
Pranav.
On Mon, Aug 9, 2010 at 12:00 PM, Pranav Modi <[email protected]> wrote:
These are the Date headers from OS and TS respectively -
Date Mon Aug 09 02:19:03 EDT 2010
Date Mon Aug 09 01:54:01 EDT 2010
TS is about 30 mins off in sending the correct EDT. Is this causing
the problem?
The OS does not send any age header.
Thanks,
Pranav
On Mon, Aug 9, 2010 at 11:14 AM, Steve Jiang <[email protected]> wrote:
Pranav Modi wrote, on 8/8/10 10:32 PM:
Age 14400
TS thinks the item is 4 hours old, is the clock on the origin server synced
with the TS host? Are the Date and Age headers served from your origin
server correct? Again, the best practice here is to emit an explicit
Expires: or Cache-Control: header from your origin server rather than force
TS using cache.config.
Via HTTP/1.0 <proxy_name> (ApacheTrafficServer/2.1.0 [cSsSfU])
The [cSsSfU] code indicates that TS thinks the document is stale and
revalidated it with the origin server (likely due to the 4 hour age). This
is documented in the Admin Guide Addendum, but I don't see it on the online
admin guide. Miles, can you get the section for "Via Header" added to the
apache docs?
--Steve
On Mon, Aug 9, 2010 at 9:59 AM, Steve Jiang <[email protected]> wrote:
This works for me. What are the full response headers you are getting
back
from TS?
--Steve
Pranav Modi wrote, on 8/8/10 11:45 AM:
Pinning content in cache for a certain period of time is not working
in my case. Data seems to be cached indefinitely.
The entries in cache.config is -
url_regex=/social/rest/activities ttl-in-cache=5m
url_regex=/social/rest/messages ttl-in-cache=5m
url_regex=/social/rest/people ttl-in-cache=3h
url_regex=/social/rest/appdata ttl-in-cache=5m
and have set the following variable to 1-
proxy.config.cache.permit.pinning
Something else needs to be done to make this work?
Thanks,
Pranav
On Thu, Aug 5, 2010 at 7:49 PM, Valerie Detweiler <[email protected]>
wrote:
Pranav -
Ideally the Cache-Control and Expires headers should be set correctly
on
the
origin servers, however you may override the origin response header
using
cache.config. For example:
url_regex=/dir/file1.html ttl-in-cache=5m
url_regex=/dir/file2.html ttl-in-cache=12h
For the full syntax please refer
to
http://trafficserver.apache.org/docs/v2/admin/files.htm#cache.config.
~valerie
----- Original Message ----
From: Pranav Modi <[email protected]>
To: [email protected]
Sent: Thu, August 5, 2010 9:10:00 AM
Subject: setting url specific caching time
Is there a way to set a specific caching time for specific url. For
example - I want data from one url to be cached for 5 mins and from
another url to be cached for 12 hours. Can it be done?
