These are the response headers -

(Status-Line)   HTTP/1.1 200 OK
MIME-Version    1.0
Server  ATS/2.1.0
Date    Mon Aug 09 01:27:45 EDT 2010
Content-Type    text/plain
Age     14400
Transfer-Encoding       chunked
Connection      keep-alive
Via     HTTP/1.0 <proxy_name> (ApacheTrafficServer/2.1.0 [cSsSfU])

Thanks,
Pranav.





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?
>>>
>>>
>>>
>>>
>>>
>

Reply via email to