Problem with PWA and google font cache

  • lenineto

    (@lenineto)


    6 years, 2 months ago

    Hi guys,
    I’ve been playing with the plugin and I’m loving it so far, but I got stuck at a problem.
    When enabling “cache assets” on the PWA, I keep getting this error:

    Failed to load https://fonts.gstatic.com/s/librefranklin/v2/jizDREVItHgc8qDIbSTKq4XkRiUf2zc.woff2: Request header field x-pagespeed-sw is not allowed by Access-Control-Allow-Headers in preflight response.

    I tried every trick in the book with NGINX to add the missing CORS header but no luck. I can’t get past this no matter what.
    If I disable “cache assets”, it works.

    I can see the call
    var e=new Request(a);e.headers.set("x-pagespeed-sw",1);
    on abtf-pwa.js, but I had no luck working it out.

    Any hints?

    Thanks and kudos on the amazing plugin.

Viewing 1 replies (of 1 total)
  • Plugin Contributor o10n

    (@o10n)

    6 years, 2 months ago

    Hi lenineto,

    Thank you very much for your feedback!

    The PWA Service Worker includes the header for requests so it’s not something that you could change on the server side. It is a bug.

    The progressive web app optimization part of the plugin will soon be published as a separate plugin, with many new features and enhanced quality and performance. The plugin will be a optimization module that can be used efficiently with other optimization modules while it will also be possible to use the PWA optimization plugin stand alone as some users have requested.

    WordPress is currently reviewing our advanced Web Font Optimization plugin. Once that plugin is published and tested, the PWA optimization plugin will be made available.

    You can follow the developments on our Github page:

    https://github.com/o10n-x/

Viewing 1 replies (of 1 total)
  • The topic ‘Problem with PWA and google font cache’ is closed to new replies.

Tags