• Resolved bornwild

    (@bornwild)


    In 3 sites with wordpress that I am using webp express the images stopped showing when I access the page and only deactivating the plugin to none, the images show correctly again.
    weird thing is that with a refresh page (F5) the images showed, but only then.
    can you help me?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter bornwild

    (@bornwild)

    something that might be important:

    adding this to .htaccess
    <filesMatch “.(ico|pdf|flv|jpg|jpeg|png|gif|svg|js|css|swf)$”>
    Header set Cache-Control “max-age=84600, public”

    causes error 500

    Plugin Author rosell.dk

    (@roselldk)

    Did it stop working after upgrading Chrome?
    Which version of Chrome are you using?

    Plugin Author rosell.dk

    (@roselldk)

    Can you supply the URL to one of these sites?

    Thread Starter bornwild

    (@bornwild)

    https://sctpower.pt/

    chrome 74.0.3729.131 64bits
    console shows
    JQMIGRATE: Migrate is installed, version 1.4.1
    (index):211 [Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://crbug.com/846170

    In gtmetrix shows site correctly and before like 1 month it was working ok.

    Plugin Author rosell.dk

    (@roselldk)

    It seems to be working alright…

    I see images when visiting with Chrome (Chromium, version 73).
    In DevTools > Network, I see that they are delivered as webp.

    The lazyloaded images which are set with CSS backgrounds are also working fine

    Ie this one:
    https://sctpower.pt/wp-content/uploads/2019/04/Efici%C3%AAncia-Energ%C3%A9tica-e1556191708857.jpg

    Gives me the following headers:

    Accept-Ranges: bytes
    Cache-Control: public, max-age:86400, stale-while-revalidate=604800, stale-if-error=604800
    Connection: Keep-Alive
    Content-Encoding: gzip
    Content-Length: 6695
    Content-Type: image/webp
    Date: Fri, 10 May 2019 15:53:05 GMT
    ETag: “2d20eaf-1a10-5887c7a6def9c-gzip”
    Expires: Sun, 09 Jun 2019 15:53:05 GMT
    Keep-Alive: timeout=5, max=150
    Last-Modified: Thu, 09 May 2019 23:04:54 GMT
    Server: Apache
    Vary: Accept-Encoding,User-Agent,Accept
    X-WebP-Express: Redirected directly to existing web

    Thread Starter bornwild

    (@bornwild)

    on first load the picture

    Request URL: https://sctpower.pt/wp-content/uploads/2019/01/Robbialac-300×149.jpg
    Request Method: GET
    Status Code: 200 OK (from memory cache)
    Remote Address: 185.2.4.130:443
    Referrer Policy: no-referrer-when-downgrade
    Accept-Ranges: bytes
    Cache-Control: public, max-age:86400, stale-while-revalidate=604800, stale-if-error=604800
    Content-Length: 4336
    Content-Type: image/webp
    Date: Fri, 10 May 2019 15:57:26 GMT
    ETag: “2d20e9d-10f0-5887c7a591f7e”
    Expires: Sun, 09 Jun 2019 15:57:26 GMT
    Last-Modified: Thu, 09 May 2019 23:04:53 GMT
    Server: Apache
    Vary: User-Agent,Accept
    X-WebP-Express: Redirected directly to existing webp
    Provisional headers are shown
    range: bytes=0-2047
    Referer: https://sctpower.pt/
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.131 Safari/537.36

    should have loaded but it doesn’t.
    if i hit ctrl+f5 the picture is loaded.

    if plugin set no none, it displays on first load.

    • This reply was modified 5 years, 6 months ago by bornwild.
    Plugin Author rosell.dk

    (@roselldk)

    Hm. That image actually shows in my browsers on first load.

    Plugin Author rosell.dk

    (@roselldk)

    Oh, I see that you have an error in the Cache-Control header.
    The part that says “max-age:86400” should be “max-age=86400”.

    Change the “:” to “=”.
    Unfortunately, I provided a default value for the “custom” option which had a “:” instead of a “=” – See https://github.com/rosell-dk/webp-express/issues/221

    Plugin Author rosell.dk

    (@roselldk)

    I did not think of correcting the invalid headers due to this wrong default value, sorry. I have added an issue for it, so it will happen in the next release: https://github.com/rosell-dk/webp-express/issues/235

    Plugin Author rosell.dk

    (@roselldk)

    Next release is here, and the issue should now be automatically fixed by the update script

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘redirect to webp stopped working in new version of chrome’ is closed to new replies.