WordPress.org

1. willshouse
   Member
   Posted 1 year ago #
   

   Getting a "400 Bad Request - Please see http://code.google.com/p/minify/wiki/Debugging " message. There is no help on the plugin's home page or in the documentation about errors or how to turn on debugging, which to me looks like it requires Firelogger. I don't want to have to use firefox and install firelogger to try and debug this. Please post some basic instructions on how to debug, or possibly even add the debugging options into the admin configuration panel. This is supposed to be the "better" version but I think I'm going back to the vanilla.

   http://wordpress.org/extend/plugins/bwp-minify/

2. OddOneOut
   Member
   Plugin Author
   Posted 1 year ago #
   

   If possible please send me a link to your website and I will see what I can do, thank you.

3. crudhunter
   Member
   Posted 1 year ago #
   

   I am seeing this problem still. Fresh downloaded plugin.
   This report was originally done 6 months ago.

   Is there a version with a fix?

   I sent this earlier on another thread with the same issue, but Re: Login, but I refreshed this one instead, since it actually has the right subject. :-)

4. crudhunter
   Member
   Posted 1 year ago #
   

   FYI..

   I just figured out what is going on..

   But first, I looked at the two earlier reports about the message.
   You probably know this already, but for the sake of this documentation, I think I should make it clear how the '400 bad request' appear.

   The Bad request message shows up instead of minified CSS, which is why people complain that the CSS is broken. It is not there.

   For example, when it calls to minimize some of the CSS files, when looking at the 'CSS code' supposedly produced by the BWP minify URL showing in the html, rather than minified CSS, it instead has this message as its sole content:

   <h1>400 Bad Request</h1><p>Please see http://code.google.com/p/minify/wiki/Debugging.</p>

   This message is from 'min/builder/index.php'.

   Solution in my case:

   Checking around in other logs I found, that it was a conflict with the the cache plugin, in my case WP Super Cache, using a CDN.

   Along the way, the cache plugin decides to manipulate the CSS/JS URLs calling on bwp-minify, and redirect them to the CDN, adding another host and directory prefix.. The '400 Bad Request' was coming from 'min', because the directory structure "over there on the CDN" is not what it expects, now with a prefix added to the path.

   Adding another filter string to the cache plugin, telling it to stay away from URLs that has bwp-minify in them fixed it. Now bwp-minify calls stay off the CDN.

Topic Closed

This topic has been closed to new replies.