Possible Bug: Missing Cache Validator for Fonts

  • Resolved dK

    (@dkristanda)


    6 years, 6 months ago

    Hi W3TC team,
    Just found a possible bug.

    GT Metrix complain about missing cache validator on fonts file.

    It seems Version 0.11.0 create a conflicting entry in .httaccess:

    snippet: “Group 1”:

    <FilesMatch "\.(asf|asx|wax|wmv|wmx|avi|bmp|class|divx|doc|docx|eot|exe|gif|gz|gzip|ico|jpg|jpeg|jpe|webp|json|mdb|mid|midi|mov|qt|mp3|m4a|mp4|m4v|mpeg|mpg|mpe|webm|mpp|otf|_otf|odb|odc|odf|odg|odp|ods|odt|ogg|pdf|png|pot|pps|ppt|pptx|ra|ram|svg|svgz|swf|tar|tif|tiff|ttf|ttc|_ttf|wav|wma|wri|woff|woff2|xla|xls|xlsx|xlt|xlw|zip|ASF|ASX|WAX|WMV|WMX|AVI|BMP|CLASS|DIVX|DOC|DOCX|EOT|EXE|GIF|GZ|GZIP|ICO|JPG|JPEG|JPE|WEBP|JSON|MDB|MID|MIDI|MOV|QT|MP3|M4A|MP4|M4V|MPEG|MPG|MPE|WEBM|MPP|OTF|_OTF|ODB|ODC|ODF|ODG|ODP|ODS|ODT|OGG|PDF|PNG|POT|PPS|PPT|PPTX|RA|RAM|SVG|SVGZ|SWF|TAR|TIF|TIFF|TTF|TTC|_TTF|WAV|WMA|WRI|WOFF|WOFF2|XLA|XLS|XLSX|XLT|XLW|ZIP)$">
    FileETag MTime Size
    <IfModule mod_headers.c>
        Header set Pragma "public"
        Header append Cache-Control "public"
         Header unset Set-Cookie
         Header set X-Powered-By "W3 Total Cache/0.11.0"
    </IfModule>
</FilesMatch>

    and immediately followed by “Group 2”

    <FilesMatch "\.(bmp|class|doc|docx|eot|exe|ico|json|mdb|webm|mpp|otf|_otf|odb|odc|odf|odg|odp|ods|odt|ogg|pdf|pot|pps|ppt|pptx|svg|svgz|swf|tif|tiff|ttf|ttc|_ttf|wav|wri|woff|woff2|xla|xls|xlsx|xlt|xlw|BMP|CLASS|DOC|DOCX|EOT|EXE|ICO|JSON|MDB|WEBM|MPP|OTF|_OTF|ODB|ODC|ODF|ODG|ODP|ODS|ODT|OGG|PDF|POT|PPS|PPT|PPTX|SVG|SVGZ|SWF|TIF|TIFF|TTF|TTC|_TTF|WAV|WRI|WOFF|WOFF2|XLA|XLS|XLSX|XLT|XLW)$">
    FileETag None
    <IfModule mod_headers.c>
         Header unset ETag
         Header unset Last-Modified
    </IfModule>
</FilesMatch>

    “Group 1” is using “FileETag MTime Size” while “Group 2” is using “FileETag None”. And it seems “Group 2” is a subset of “Group 1”. (Those group of code are the last 2 FilesMatch block before mod_header)

    If I remember correctly, the previous version did have a similar second group but only to remove the Last-Modified header (without “FileETag None” and “Header unset ETag”)

    So, I remove those 2 commands (the one removing the Etag at 2nd group and all good)

    Hopefully, it is just simple bug otherwise I am the one that might have some conflicting setting 🙂

    If I did not change any setting W3TC will not recreate my .htaccess, right? please? LOL….

    Awesome plugin. Internet will never be the same without W3TC!! Literally…
    Thanks.
    Cheers,
    Denis

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    6 years, 6 months ago

    Hello @dkristanda

    Thank you for bringing this to our attention and I am happy to assist you with this.
    We’ve checked this and it appears that when compatibility mode is enabled this may happen.
    Go to Performance>Page cache>Advanced and untick the compatibility mode and see if the issue persists.
    Usually, the compatibility mode is not required in modern hosting accounts.
    I’ve also created a ticket on your behalf in our Github public repository so you may check the progress there regularly.

    Thread Starter dK

    (@dkristanda)

    6 years, 6 months ago

    Thanks for your reply and the github link

    I think what happen here is that the developer has removed the compatibility mode but havent fully strip the code.

    The only checkbox in Page Cache Advance is “late initialization” and “late caching”

    Also the exact coding is repeated at the Browser Cache plugin. Might be useful info for the developer if they want to strip it clean.

    Thanks again!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    6 years, 6 months ago

    Hello @dkristanda

    Just to confirm, In Performance>Page Cache>Advanced section you are not seeing “Compatibility mode”?
    Can you please check this image and confirm that?

    Thread Starter dK

    (@dkristanda)

    6 years, 6 months ago

    Yes, confirmed.. no pg cache compatibility.

    here is my screen capture

    View post on imgur.com

    weird?

    thanks!
    Denis

    ps. I hv submit another bug I found – quite big one/obvious.. but on hold by moderator due to lots of ‘dummy’ link as illustration. hope can be released soon.. if ever…

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    6 years, 6 months ago

    Hello @dkristanda

    Thanks for the information.
    This is very strange. “Maximum lifetime of cache objects:” should be located in Performance>Database cache.
    Here is the screenshot of the advanced sub-box of Performance>Page Cache (how it’s supposed to be).
    Can you please share a similar screenshot?

    Thread Starter dK

    (@dkristanda)

    6 years, 6 months ago

    Hmm…so I was denied 2 options… lol

    Here it is… PageCache Advance box

    Is it interference from another plugin?
    The only thing that I installed related to W3TC is the helper plugin to help me do the manual mode “W3TC Minify Helper Version 1.0.0.1 By Magenta Cuda” which did help me get better js deferral. But have tried to disable this plugin, no effect to the missing options.

    Thanks
    Regards,
    Denis

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    6 years, 6 months ago

    Hello @dkristanda

    W3 Total Cache generates those rules only in compatibility mode.
    The compatibility mode option is shown only when disk-enhanced is used. What caching method are you using? Maybe Memcached or Redis? If you have had Disk: Enhanced enabled and then switched to something else there is a possibility that the Compatibility mode was selected and now affects browser cache rules historically.
    Two things that you can do potentially. You can switch back to Disk: Enhanced save all settings and then disable compatibility mode, save all settings and purge caches. The other thing that you can do is to manually remove W3TC rules from .htaccess and leave the .htaccess only with WP default rules. This will allow W3 Total Cache to write new set of rules to your .htaccess file.
    I hope this helps!

    Thread Starter dK

    (@dkristanda)

    6 years, 6 months ago

    OK. That explained it.
    Thanks heaps!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    6 years, 6 months ago

    Hello @dkristanda
    You are most welcome!
    We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users. Thank you for your help!

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

The topic ‘Possible Bug: Missing Cache Validator for Fonts’ is closed to new replies.