• Resolved muchmuch11

    (@muchmuch11)


    I tried Brotli on my Nginx, installed successfully, I tried to enable it on W3TC, it works (despite have bug, but not this one that I reported, because I want to reconfirm it) and sending Brotli encoded files (br), now I tried to disable Brotli (for all files), restarting Nginx, the result is W3TC still creating Brotli files on minified cache. I tried to remove Brotli modules from main nginx.conf, W3TC still creating Brotli because it still detect PHP extension for Brotli.

    I haven’t tried to disable PHP Brotli extension, because it should be enough to stop Brotli creation from W3TC dashboard.

    Is there plan to fix this soon?

    Thanks

    • This topic was modified 5 years ago by muchmuch11.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter muchmuch11

    (@muchmuch11)

    I just tried to disable Brotli PHP extension, once it’s disabled, W3TC stop creating Brotli minified files. So Brotli option for CS/JSS on W3TC dashboard not working.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @muchmuch11

    I am sorry about the issue you are experiencing and I am happy to help.
    We are investigating this and will reply as soon as we check!
    Thank you for your patience.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @muchmuch11

    I’ve spoken with the team and tested this. It’s a way how third-party minify library works. When it’s able to compress using method browser asks to – it compresses. So disabling the Brotli PHP extension is the only way to stop that.
    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Brotli on Nginx bug’ is closed to new replies.