Support » Plugin: W3 Total Cache » Bug: HTTP/2 Push Not Working with CDN

  • Gulshan Kumar

    (@thegulshankumar)



    Hi,

    I had already reported this issue, but received no response. I hope, this time you find this.

    Steps to reproduce the bug
    1. Assuming, you have already configured cdn.example.com via W3TC plugin
    2. Go to Minify > Enable HTTP/2 push for CSS and JS > Purge Cache
    3. See HTTP header for the Document request and console logs

    Proof of Concept

    1. Link header
    link:</wp-content/cache/minify/a1290.js>; rel=preload; as=script, </wp-content/cache/minify/2b222.css>; rel=preload; as=style

    2. Console logs.

    The resource https://www.example.com/wp-content/cache/minify/2b222.css was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it wasn’t preloaded for nothing.

    The resource https://www.example.com/wp-content/cache/minify/a1290.js was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it wasn’t preloaded for nothing.

    Expected
    1. Link header
    link:<https://cdn.example.com/wp-content/cache/minify/a1290.js>; rel=preload; as=script, <https://cdn.example.com/wp-content/cache/minify/2b222.css>; rel=preload; as=style

    This must be fixed early.

    Thanks & Regards,
    Gulshan

Viewing 1 replies (of 1 total)
  • Pat

    (@fortythousandmiles)

    I am noticing this issue too. It also makes GTmetrix pagespeed score drop significantly because it sees the files as duplicates served from different resources.

    Thank you Gulshan for identifying the issue, this pagespeed thing was driving me mad. At least I can turn of HTTP/2 push for now.

Viewing 1 replies (of 1 total)
  • The topic ‘Bug: HTTP/2 Push Not Working with CDN’ is closed to new replies.