Opened 2 years ago
Last modified 14 months ago
#57349 new enhancement
Page cache is not detected but the server response time is OK
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 6.0.1 |
| Component: | Site Health | Keywords: | reporter-feedback |
| Focuses: | Cc: |
Description
New site health feature that reports on page cache says "Page cache is not detected but the server response time is OK"
Later expresses that"Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:
cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status."
I do happen to have cache control expires age less modified and e-tags. But these are applied by nginx reverse proxy. Wondering why they're not detected.. When it checks the page is it running it by using localhost? Or does it try from the domain name? I think it should be set up to make a request to the actual domain name if it does not say that it would get a more accurate view of the headers.
Can you share a link, so that we can take a look at the headers? Maybe the support forums is a better place for questions like this. If the outcome of the discussion there is, that you encountered a bug, we can go on here. But this needs more information about the environment.