• My site health report is giving the following message:

    ‘Unable to detect page cache due to possible loopback request problem. Please verify that the loopback request test is passing. Error: Not Found (Code: http_404)

    Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

    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-controlexpiresagelast-modifiedetagx-cache-enabledx-cache-disabledx-srcache-store-statusx-srcache-fetch-status.

    This is still showing after our hosting provider added the following to the wp-config file to enable caching rather than using a plugin as we were experiencing problems with plugins.

    #WessexIT – Added from support ticket T20230606.0186

    define( ‘ ENABLE_CACHE’ , TRUE);

    define( ‘ WP_MEMORY_LIMIT’ , ‘256M’);

    /

    As this has not worked I’d like to go back to trying to use a caching plugin instead but if I enable one and set it up for pache caching then the message still shows as no page cache detected.

    What do I need to do to get it working please?

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator t-p

    (@t-p)

    Unable to detect page cache due to possible loopback request problem. Please verify that the loopback request test is passing

    If loopback failing, ask your host why loopback is failing.
    Also ask if they can update Curl in case you are running an outdated version.

    Thread Starter emmabrown1012

    (@emmabrown1012)

    Thank you for your reply. I’ve checked the site health again and the loopback request test is passing.

    I’ve sent a message to our host to see if there is a curl update.

    Is there anything else I can try?

    Thank you.

    Thread Starter emmabrown1012

    (@emmabrown1012)

    The curl is at the latest version.

    Our hosting providers sent the following:

    ‘I expect a URL rewrite is affecting it somewhere, giving a 404 and then you also have a plugin to redirect 404’s to your homepage. I can’t spot anything immediately in the hosting environment (nginx / apache configs) so that error is likely caused by either something in htaccess or within wordpress itself.’

    I don’t know where to start looking or what I’m looking for. Can you help?

    Thank you.

    Thread Starter emmabrown1012

    (@emmabrown1012)

    This is everything in the htaccess file:

    Leverage Browser Caching in WordPress via .htaccess
    
    FileETag MTime Size AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css application/xml application/xhtml+xml application/rss+xml application/javascript application/x-javascript ExpiresActive On ExpiresByType text/html "access 600 seconds" ExpiresByType application/xhtml+xml "access 600 seconds" ExpiresByType text/css "access 1 month" ExpiresByType text/javascript "access 1 month" ExpiresByType text/x-javascript "access 1 month" ExpiresByType application/javascript "access 1 month" ExpiresByType application/x-javascript "access 1 month" ExpiresByType application/x-shockwave-flash "access 1 month" ExpiresByType application/pdf "access 1 month" ExpiresByType image/x-icon "access 1 year" ExpiresByType image/jpg "access 1 year" ExpiresByType image/jpeg "access 1 year" ExpiresByType image/png "access 1 year" ExpiresByType image/gif "access 1 year" ExpiresDefault "access 1 month"
    
    Leverage Browser Caching in WordPress via .htaccess
    
    Require all denied Order deny,allow Deny from all
    
    RewriteEngine On RewriteCond %{REQUEST_URI} ^/?wp-content/+debug.log$ RewriteRule .* - [F,L,NC]
    Require all denied
    Order deny,allow Deny from all

    BEGIN ShortPixelWebp The directives (lines) between "BEGIN ShortPixelWebp" and "END ShortPixelWebp" are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten. END ShortPixelWebp BEGIN All_404_marker_comment_image RewriteOptions inherit
    RewriteEngine on RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f RewriteRule .(gif|jpe?g|png|bmp) https://ssdsafety.co.uk/wp-content/uploads/2017/08/ssd-150x150.jpg [NC,L] END All_404_marker_comment_image BEGIN WordPress The directives (lines) between "BEGIN WordPress" and "END WordPress" are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten. RewriteEngine On RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress BEGIN FRedirect_ErrorDocument The directives (lines) between "BEGIN FRedirect_ErrorDocument" and "END FRedirect_ErrorDocument" are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten. ErrorDocument 404 /index.php?error=404 END FRedirect_ErrorDocument
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Caching error’ is closed to new replies.