WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] [Plugin: CSS-JS-Booster] css compressed, js not (5 posts)

  1. futtta
    Member
    Posted 4 years ago #

    when looking at firebug 'net' output, i noticed that the output of booster_css.php is compressed (gzip), but the javascript of booster_js.php is not.

    doing a dump of response headers in lynx confirms:

    # lynx -dump -head "http://blog.futtta.be/wp-content/plugins/css-js-booster/booster_js.php?dir=../audio-player/assets/audio-player.js,booster_cache/5840b5ad82febee045c9fb184c12853d_plain.js,../lifestream/lifestream.js&js_minify=0&nocache=1264649632"
    HTTP/1.1 200 OK
    Date: Wed, 17 Mar 2010 12:19:10 GMT
    Server: Apache
    Cache-Control: max-age=2592000, public
    Expires: Thu, 15 Apr 2010 23:19:10 GMT
    Connection: close
    Content-Type: text/javascript

    # lynx -dump -head "http://blog.futtta.be/wp-content/plugins/css-js-booster/booster_css.php?dir=../../themes/journalist/style.css,../sociable/sociable.css,../lifestream/themes/default/media/lifestream.css&nocache=1264417257"
    HTTP/1.1 200 OK
    Date: Wed, 17 Mar 2010 12:19:14 GMT
    Server: Apache
    Cache-Control: max-age=2592000, public
    Expires: Thu, 15 Apr 2010 23:19:14 GMT
    Vary: Accept-Encoding
    Content-Encoding: gzip
    Content-Length: 20
    Connection: close
    Content-Type: text/css

    any idea what is going wrong?

    http://wordpress.org/extend/plugins/css-js-booster/

  2. futtta
    Member
    Posted 4 years ago #

    for those wanting to check for themselves; my blog is at http://blog.futtta.be/, check the output of firebug (or a similar tool) to see the difference in http response headers for booster_js.php and booster_css.php.

  3. Schepp
    Member
    Posted 4 years ago #

    That's a real good question. On my test-wordpress-blog here, it works. And it should work the same way as the CSS-part, as they both share a the same commands in regards to GZIP-compresion. So I suppose there must be some local thing, like an interference with some other plugin or a maybe an .htaccess-command or so. Perhaps you can dig a bit deeper and find the trigger for this behavior?

  4. futtta
    Member
    Posted 4 years ago #

    ok, went digging found the problem: it was located in .htaccess indeed!

    following config guidelines from wp-super-cache i wanted to disable php output compression (cfr. q21 in wp super cache faq) and added

    php_flag zlib.output_compression off

    to my .htaccess. removing that line fixes the problem as described above. still .. weird that this setting affects booster_js.php and not booster_css.php, no?

  5. Schepp
    Member
    Posted 4 years ago #

    You are right, it would be logical that it is the same for booster_js.php and not booster_css.php. Don't know what happended there.

Topic Closed

This topic has been closed to new replies.

About this Topic