It didn't work for me, either. I'm back to using the stuff listed below. On Wed, Mar 26, 2008 at 7:16 PM, Andy Skelton <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 26, 2008 at 6:22 PM, Benoit Bisson <[EMAIL PROTECTED]> > wrote: > > The image uploading issue that results in an http error has been brought > up > > repeatedly, and answers on the topic repeatedly point towards either > add-on > > issues or the possibility of the user not having the latest Flash > version. > > Well, before any user starts pulling out hair, I believe it's Brent > Logan > > who first posted this slight change to the htaccess file: > > > > > SecFilterEngine Off > > > SecFilterScanPOST Off > > > > That worked like a charm for me, using WP2.5 RC2, with either FF or IE, > > That's good, but before we turn that into a core patch or even a > recommendation for other users we should make sure it's as minimal as > possible. The way I read it, those lines turn off the security filter > engine for everything at or below that directory level. Can we get the > desired result within just the desired scope? And what happens when > mod_security is not loaded? (Hint: 500) > > This is something I crafted from a few google hits: > > <IfModule mod_security.c> > SecFilterSelective "REQUEST_URI" "wp-admin/async-upload.php" "allow,nolog" > </IfModule> > > Would you mind testing it? I don't have mod_security so I need some > help on this one. > > Cheers, > Andy > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > -- Brent Logan 503.828.1772 _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
