On Nov 30, 2006, at 3:01 PM, Riccardo Cohen wrote:

> do you mean that caching should be configured only on front server ?

No, having the proxy cache on the backend is useful, but the gain is  
more dramatic if you enable it on the front server because you avoid  
sending the request to the backend at all (so at very least, you save  
on networking.)

-- Scott

>
> Scott Ferguson wrote:
>> On Nov 30, 2006, at 8:27 AM, Riccardo Cohen wrote:
>>
>>> I think I made a mistake.
>>> There is no link between browser cache and server cache. If the
>>> browser decide to suppress
>>> caching in https, I still can set caching on the server, that will
>>> optimize disk access on
>>> the server. So keeping <cache-mapping> is still a good idea, even
>>> on https.
>>>
>>> Am I right ?
>>
>> That's correct.
>>
>> For example, if you were using Resin as a web-server/load-balancer,
>> then the <cache-mapping> would cache content on the front-end web-
>> server, saving traffic to the backend servers.
>>
>> -- Scott
>>
>>> Riccardo Cohen wrote:
>>>> thanks for the information ! I'll simply remove the cache from my
>>>> "full https" app !
>>>>
>>>> Richard Paul wrote:
>>>>> Ignore this request, Firefox has caching disable by default for  
>>>>> ssl
>>>>> connections.
>>>>> In about:config you can set the value for
>>>>> "browser.cache.disk_cache_ssl"
>>>>> to true to enable the ssl cache.
>>>>>
>>>>> Richard Paul wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I am attempting to set the browser's expires value for our
>>>>>> static resources.
>>>>>> I have added the following to resin.conf under web-app-default:
>>>>>>
>>>>>>       <cache-mapping url-pattern="*.gif" expires="7D"/>
>>>>>>       <cache-mapping url-pattern="*.png" expires="7D"/>
>>>>>>       <cache-mapping url-pattern="*.jpg" expires="7D"/>
>>>>>>       <cache-mapping url-pattern="*.swf" expires="7D"/>
>>>>>>       <cache-mapping url-pattern="*.js" expires="1D"/>
>>>>>>
>>>>>> When using HTTP the expires value is set correctly, but when
>>>>>> using HTTPS
>>>>>> no expires value is set causing the resource not to be cached.
>>>>>> Is this a bug or am I missing a configuration option?
>>>>>>
>>>>>> I have tried this on resin-pro-3.0.19 and resin-pro-3.0.22.
>>>>>> Suse linux 10.0, Java 1.5.
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Richard.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> resin-interest mailing list
>>>>>> resin-interest@caucho.com
>>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>>
>>>>> _______________________________________________
>>>>> resin-interest mailing list
>>>>> resin-interest@caucho.com
>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>
>>> -- 
>>> Très cordialement,
>>>
>>> Riccardo Cohen
>>> ligne directe : 02-47-49-63-24
>>> -------------------------------------------
>>> Articque
>>> http://www.articque.com
>>> Moulin des Roches
>>> 37230 Fondettes - France
>>> tel : 02-47-49-90-49
>>> fax : 02-47-49-91-49
>>>
>>> _______________________________________________
>>> resin-interest mailing list
>>> resin-interest@caucho.com
>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>
>>
>> _______________________________________________
>> resin-interest mailing list
>> resin-interest@caucho.com
>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>
>
> -- 
> Très cordialement,
>
> Riccardo Cohen
> ligne directe : 02-47-49-63-24
> -------------------------------------------
> Articque
> http://www.articque.com
> Moulin des Roches
> 37230 Fondettes - France
> tel : 02-47-49-90-49
> fax : 02-47-49-91-49
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest


_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to