• Resolved realpetchicken

    (@realpetchicken)


    I am still getting these errors after enable cache and all of SG Optimizer features. I also checked my .htaccess and there isn’t any expiry headers there, i have purge cache etc.

    Any help would be appreciated.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    What errors?

    Thread Starter realpetchicken

    (@realpetchicken)

    @hristo-sg Sorry, errors on pingdom.com

    https://prnt.sc/151axc4

    # HTTPS forced by SG-Optimizer
    <IfModule mod_rewrite.c>
    RewriteCond %{HTTP_HOST} !^www\. [NC]
    RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteCond %{HTTPS} off
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    </IfModule>
    # END HTTPS
    # START PHP VERSION CHANGE forced by SG Optimizer
    # END PHP VERSION CHANGE
    # 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.
    <IfModule mod_rewrite.c>
    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]
    </IfModule>
    # END WordPress
    # Block WordPress xmlrpc.php requests
    <Files xmlrpc.php>
    order deny,allow
    deny from all
    </Files>
    # Wordfence WAF
    <Files “.user.ini”>
    <IfModule mod_authz_core.c>
    Require all denied
    </IfModule>
    <IfModule !mod_authz_core.c>
    Order deny,allow
    Deny from all
    </IfModule>
    </Files>
    # END Wordfence WAF

    # SGO Unset Vary
    Header unset Vary
    # SGO Unset Vary END`

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    Expires are handled by the NGINX and not by .htaccess rules. Which elements lack expires? I bet they are 3rd party resources outside of your hosting account…

    Thread Starter realpetchicken

    (@realpetchicken)

    @hristo-sg How can i check which 3rd party resources are lacking expires?

    Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    Marking as resolved

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Expiry Headers issue’ is closed to new replies.