You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficserver.apache.org by Esmq <es...@163.com> on 2013/05/25 13:22:07 UTC

cache separately for ervery client when OS return set cookie ?

hi,all


i use ts(v3.2.4) for reverse proxy, and set  cache_responses_to_cookies to 4 in records.config,  which give the following means:
   #   4 - cache for all but text content-types except OS response
   #       without "Set-Cookie" or with "Cache-Control: public"


now i have set up a testing  original server that will returning the  Set-Cookie header,


and i found that ts will cache separately for ervery client when OS return set cookie...


Client A -> TS -> OS (TS cache the response to obj1)
Client B -> TS -> OS (TS cache the response to boj2)


why A and B not use the same cached obj? 


Re:Re:Re: cache separately for ervery client when OS return set cookie ?

Posted by Esmq <es...@163.com>.
pretty sorry for my mistake... 


i got the point now.


the previous mistake is for i had set vary_default_images to User-Agent, and test on different machine (User-Agent) ...





At 2013-05-25 19:44:25,Esmq <es...@163.com> wrote:

hi,

tow more strange things:


1) cached obj1 and obj2 not return Set-Cookie to client;


2) cached obj1 and obj2 were shared by different clients (some clients use obj1, some other clients use obj2)




At 2013-05-25 19:31:19,"Reindl Harald" <h....@thelounge.net> wrote:
>Am 25.05.2013 13:22, schrieb Esmq:
>> i use ts(v3.2.4) for reverse proxy, and set  cache_responses_to_cookies to 4 in records.config,  which give the
>> following means:
>>    #   4 - cache for all but text content-types except OS response
>>    #       without "Set-Cookie" or with "Cache-Control: public"
>> 
>> now i have set up a testing  original server that will returning the  Set-Cookie header,
>> 
>> and i found that ts will cache separately for ervery client when OS return set cookie...
>> 
>> Client A -> TS -> OS (TS cache the response to obj1)
>> Client B -> TS -> OS (TS cache the response to boj2)
>> 
>> why A and B not use the same cached obj? 
>
>because it would be a very bad idea if B get the session-cookie from A?
>

Re:Re: cache separately for ervery client when OS return set cookie ?

Posted by Esmq <es...@163.com>.
hi,

tow more strange things:


1) cached obj1 and obj2 not return Set-Cookie to client;


2) cached obj1 and obj2 were shared by different clients (some clients use obj1, some other clients use obj2)




At 2013-05-25 19:31:19,"Reindl Harald" <h....@thelounge.net> wrote:
>Am 25.05.2013 13:22, schrieb Esmq:
>> i use ts(v3.2.4) for reverse proxy, and set  cache_responses_to_cookies to 4 in records.config,  which give the
>> following means:
>>    #   4 - cache for all but text content-types except OS response
>>    #       without "Set-Cookie" or with "Cache-Control: public"
>> 
>> now i have set up a testing  original server that will returning the  Set-Cookie header,
>> 
>> and i found that ts will cache separately for ervery client when OS return set cookie...
>> 
>> Client A -> TS -> OS (TS cache the response to obj1)
>> Client B -> TS -> OS (TS cache the response to boj2)
>> 
>> why A and B not use the same cached obj? 
>
>because it would be a very bad idea if B get the session-cookie from A?
>

Re: cache separately for ervery client when OS return set cookie ?

Posted by Reindl Harald <h....@thelounge.net>.
Am 25.05.2013 13:22, schrieb Esmq:
> i use ts(v3.2.4) for reverse proxy, and set  cache_responses_to_cookies to 4 in records.config,  which give the
> following means:
>    #   4 - cache for all but text content-types except OS response
>    #       without "Set-Cookie" or with "Cache-Control: public"
> 
> now i have set up a testing  original server that will returning the  Set-Cookie header,
> 
> and i found that ts will cache separately for ervery client when OS return set cookie...
> 
> Client A -> TS -> OS (TS cache the response to obj1)
> Client B -> TS -> OS (TS cache the response to boj2)
> 
> why A and B not use the same cached obj? 

because it would be a very bad idea if B get the session-cookie from A?