Memcache expiry set to 1981

  • I’m using memcached to cache my site and recently I hav noticed lately that expires setting on the cache is set to 1981. From my understanding this would indicate that the server never would serve up a cached version because it sees it as state.

    Live site at: https://www.d2l.com/

    Here is the dump

    <!– Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/

    Object Caching 6093/6959 objects using memcache
    Page Caching using memcache
    Page cache debug info:
    Engine: memcache
    Cache key: 7527492c768fdf1fc52c1ac6cf06b892_ssl
    Creation Time: 1486662243.000s
    Header info:
    Set-Cookie: _icl_current_language=en; expires=Fri, 10-Feb-2017 17:44:02 GMT; Max-Age=86400; path=/
    Expires: Thu, 19 Nov 1981 08:52:00 GMT
    Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
    Pragma: no-cache
    Set-Cookie: _icl_current_language=en; expires=Fri, 10-Feb-2017 17:44:02 GMT; Max-Age=86400; path=/
    Content-Type: text/html; charset=UTF-8
    Link: <https://staging2.d2l.d2l/wp-json/&gt;; rel=”https://api.w.org/&#8221;
    Link: <https://staging2.d2l.d2l/&gt;; rel=shortlink
    Content Delivery Network via Amazon Web Services: S3: assets.d2l.com

    Served from: staging2.d2l.d2l @ 2017-02-09 12:44:03 by W3 Total Cache –>

Viewing 3 replies - 1 through 3 (of 3 total)

  • Do you talking about:

    Set-Cookie: _icl_current_language=en; expires=Fri, 10-Feb-2017 17:44:02 GMT; Max-Age=86400; path=/
    Expires: Thu, 19 Nov 1981 08:52:00 GMT

    It’s not memcache but http header cookie and it’s not w3tc but another plug-in (wpml).

    • This reply was modified 8 years, 1 month ago by nigro.simone.
    Thread Starter erikfrye

    (@erikfrye)

    I see that but the cookies that you see there from wpml is set to expire Feb 2017. I think the link below

    Expires: Thu, 19 Nov 1981 08:52:00 GMT

    is what the page cache is set to expire?

    Perhaps I’m wrong.

    Expires is a browser cache header. It’s indicating to the browser to not cache the page (1981) but to serve up a fresh one by hitting your server which in your case since you are using a cache engine will serve back a cache version of the page. Is your Browser Cache option enabled in Performance > General Settings? Its there where u set the Expires time.

    From what i see, from your headers, it looks like its serving a cached page fine.

    • This reply was modified 8 years, 1 month ago by Kimberly.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Memcache expiry set to 1981’ is closed to new replies.