Forum Discussion

Eireann78_19953's avatar
Eireann78_19953
Icon for Nimbostratus rankNimbostratus
Mar 30, 2009

ramcache honoring headers

BIG-IP 9.4.5 Build 1086.1 Hotfix HF2

 

 

Hi,

 

I have enabled ramcache on a profile applied to a VIP.

 

 

For the ignore headers option I have chosen None which Specifies that the system honors all Cache-Control headers. All others setting are default so the max age setting on the F5 is 60mins.

 

 

On the application that is passing through the VIP the max age header is set to 30mins. This header passes correctly to the browser but when I look at the cache on the F5 itself it uses the default max age and not the one set from the browser.

 

 

I want the F5 to behave like a public cache and honor the settings from the application. Has anyone come across this before?

 

 

On another aside I have come across different versions of the meaning of some of the settings.

 

 

For the option Cache-Control:max age the help on the F5 has the following "Cache-Control:max-age: Specifies that the system acknowledges only the Cache-Control:max-age header." While from documentation on the site I found the opposite "Specifies that the system ignores only the Cache-Control:max-age header."

 

 

Tks,

 

D
application delivery
performance
wa

4 Replies

Sort By
  • Dawn_Parzych_20's avatar
    Dawn_Parzych_20
    Apr 02, 2009
    The Ignore No-Cache options in the RAM cache profile apply only to Cache-Control headers in the request not cache control headers in the response. If the client sends a Cache-Control: no-cache header such as what occurs when hitting CTRL-Refresh and the ignore none option is selected the content will not be served from RAM cache, if ignore all is selected the content will be served from RAM cache.

     

     

    From what I have seen in testing this RAM cache will always follow what is configured in the profile and not what is sent from the server for max-age or s-maxage values.

     

     

    WebAccelerator which is an application aware cache can be configured to either follow or ignore Cache-Control headers in the response.