For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Terrence's avatar
Terrence
Icon for Nimbostratus rankNimbostratus
May 27, 2014

Why is this not being Cached

I have banged my head for two days now attempting to figure out what and why this isnt being cached by the F5. It appears that its a long dark road when you are attempting to figure out why things arent hapenning in regards to wam.

> GET /myCOMPANY/node/6 HTTP/1.1
> User-Agent: curl/7.35.0
> Host: t-www.COMPANY.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Tue, 27 May 2014 20:11:01 GMT
* Server Apache is not blacklisted
< Server: Apache
< X-Drupal-Cache: HIT
< Content-Language: en
< Link: ; rel="canonical",; rel="shortlink"
< X-Generator: Drupal 7 (http://drupal.org)
< Cache-Control: no-cache
< Last-Modified: Tue, 27 May 2014 13:37:24 +0000
< Expires: Tue, 27 May 2014 20:11:03 GMT
< Vary: Cookie,Accept-Encoding
< X-XSS-Protection: 1; mode=block
< Content-Type: text/html; charset=utf-8
< Set-Cookie: BIGipServerCOMPANY_CORPORATE_DEV.app~COMPANY_CORPORATE_DEV_pool=rd2o00000000000000000000ffff8ed6f029o80; path=/
< Accept-Ranges: none
< X-WA-Info: [V2.S10201.A5777.P45671.N13710.RN0.U2407940255].[OT/html.OG/pages].[P/0.3].[O/0.2].[EH1/0].[DH1/0].[C/P]
< Transfer-Encoding: chunked
<
{ [data not shown]
* Connection 0 to host t-www.COMPANY.com left intact

wainfodecode returns the following:

V2: X-WA-Info Format Version
    S10201: Response was served from the origin web server, because the request was for new content.
    A5777: Application: /Common/DRUPAL-TEST.app/DRUPAL-TEST_aam
    P45671: Local-policy: /Common/Generic Policy - MyCompany
    N13710: Request Policy Node: Pages
    RN0: Response match did not supersede request match
    UCI hash: da7ae1cc
    Object type: html
    Object group: pages
    Request served from TMM: 0.2
    Request owned by TMM: 0.3
    Entity hit count (local/remote): 1/0
    Document hit count (local/remote): 1/0
    Document cacheable, but not seen enough to cache.

I am at my wits end and I have no understanding of why, or how to make this cache.

1 Reply

  • It appears that I have found the root of my issue. And it was completely by accident. I was browsing the site and found a page that was larger than the Maximum Object size of the default profile(50000 bytes). This returned a "This page it to large to cache" in X-WA-Info. I increased the size to 80000 to see if I could get a page to cache(I also fiddled with the parent profile). And miraculously all the pages that would not cache before started caching. I verified this by setting the profile back to 50000 and sure enough the pages started not caching again.

     

    It appears to be a bug perhaps in X-WA-Info as after putting the number back to 50000 the X-WA-Info once again returned: [V2.S10201.A5777.P45671.N89193.RN0.U3665486284].[OT/html.OG/pages].[P/0.3].[O/0.3].[EH3/0].[DH3/0].[C/P] S10201: Response was served from the origin web server, because the request was for new content.

     

    Setting it back to 80000 and the pages started caching again.

     

    I am running 11.4.1 in a vcmp configuration on v5200's if that matters