Identify mod_Pagespeed as cache in the Persistent Object Cache Health Check

  • Resolved ABCdatos

    (@abcdatos)


    2 years, 2 months ago

    Hi, folks:

    The two alternatives of headers created by mod_pagespeed shall be taken as an operative cache evidence. This module always operate creating object cache after optimization.

    As can read in https://www.modpagespeed.com/doc/configuration#XHeaderValue

    By default, PageSpeed adds an header, X-Mod-Pagespeed in Apache, X-Page-Speed in Nginx

    Distinct values may be configured, the header always is present when enabled.

    Happy new year!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi @abcdatos,

    Thanks for reaching out. While I may need to check this with the team do you want to provide more insights into this and I can go ahead also create an issue or enhancement on the plugins GitHub repository?

    You can also submit your own if you wish, while adding additional context for the team to review.

    And happy new year to you also!

    Thread Starter ABCdatos

    (@abcdatos)

    Hi @jamesosborne,

    I’m going to create some testing environment to get exact original messages and clear context prior to returning here to post them or going to GitHub on the following days.

    Best regards!

    Plugin Support James Osborne

    (@jamesosborne)

    Sounds good, much appreciated @abcdatos! If opening a GitHub issue or enhancement request there are some preformatted sections, such as steps to reproduce and screenshots. These can come in use when the team is reviewing.

    Best of luck!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Identify mod_Pagespeed as cache in the Persistent Object Cache Health Check’ is closed to new replies.