• Hi,

    I am using plugin and recently upgrade (Version 0.14.3) it shown “It seems your server setup does not support headers in .htaccess. You should either fix this (install mod_headers) or deactivate the “Enable direct redirection to existing converted images?” option. Otherwise the Vary:Accept header will not be added and this can result in problems for users behind proxy servers (ie used in larger companies)”

    and the litespeed is already have mod_headers. Please advise.

    Regards,

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author rosell.dk

    (@roselldk)

    Ok, could mean that the mod_header test misfired. Or it could mean that mod_headers isn’t actually working properly on your system. I shall do some testing to shed light on this.

    Anyway, WebP Express uses this test when generating the .htaccess rules. If the test has failed, there wil NOT be added rules which takes care of adding the Vary:Accept header.
    It will be a big problem if you are on a CDN.
    I’m not sure if the proxy server thing is a big problem or not. But it might.

    Until the issue has been examined, you can add the following manually to you .htaccess (outside the # BEGIN WebP Express block):

    The following will add Vary:Accept to ALL responses:

    
    <IfModule mod_headers.c>
        Header append "Vary" "Accept" env=ADDVARY
    </IfModule>
    

    Or, if you have mod_setenvif, you may want to add this instead, which only adds Vary:Accept to image responses:

    
    <IfModule mod_setenvif.c>
        SetEnvIf Request_URI "\.(jpe?g|png|webp)$" ADDVARY
    </IfModule>
    <IfModule mod_headers.c>
        Header append "Vary" "Accept" env=ADDVARY
    </IfModule>
    

    Hi, I have the same issue. WebP Express 0.17.2 on LiteSpeed with mod_headers gives the same warning. It’s a multisite install, and the plugin is network-active if that’s relevant.

    I’ll try the solution you provided but it’d be nice to not have to muck around in .htaccess by hand ?? If you’d like more info about my environment/config, please let me know!

    • This reply was modified 5 years, 1 month ago by uryga.

    @anas_xrt if it’s still relevant to you, try webp-express 0.17.3 – i’ve submitted a patch that solves the issue for me.

    • This reply was modified 4 years, 9 months ago by uryga.
    Plugin Author rosell.dk

    (@roselldk)

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error Mod_header with LiteSpeed Enterprise’ is closed to new replies.