xmlrpc solution on shared hosting

  • A lot of people have been having trouble getting their blog client (Journler for instance on OS X) to play nice with the Metaweblog API (xmlrpc.php) when wordpress is installed on a shared hosting service. I found a solution to this on these forums, but it was not easy to find, so i am re-posting here.

    If you are getting errors connecting to xmlrpc.php in your client, try adding the following to your .htaccess file.

    <Files xmlrpc.php>
    SecFilterInheritance Off
    </Files>

    Those having trouble with Journler in particular might also find this thread of interest: https://www.journler.com/community/forums/viewtopic.php?p=10460#10460

Viewing 3 replies - 1 through 3 (of 3 total)

  • This solution worked well for me when my server was using php4, but I get Internal Server Errors when on php5.

    The error returned is:

    Invalid command ‘SecFilterInheritance’, perhaps misspelled or defined by a module not included in the server configuration

    The server is using php 5.2.5, and my host has confirmed the command is not available anymore (https://forums.wirenine.com/showthread.php?p=1522#post1522).

    Is there another way to make the Metaweblog API work on php5? If it makes a difference, I’m trying to use Ma.gnolia’s blog posting feature (which worked fine with the SecFilterInheritance Off command on php4).

    It being unavailable has nothing to do with the version of PHP you are on. That directive is disabling mod_security, an Apache module that has absolutely nothing to do with PHP.

    Its also for mod_security 1.9x, which is pretty outdated.

    Ask your host if they are running mod_security 2?

    After searching the web a bit and some back and forth with my host, I’ve found the problem. It seems my host upgraded to ModSecurity 2, and disabling it is (a) no longer possible through the htaccess file and (b) if they disable it for me, it would be for my entire website rather than just the xmlpc file.

    If anyone else is having this problem, first try one of the following:

    If you get crazy errors with those fixes, it’s likely ModSecurity can only be disabled through the Apache config file, which must be done by your host. Again, this can only be done for your entire site and not just the Metaweblog API file (xmlpc.php, in most cases), so you’ll need to consider the security risk before requesting it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘xmlrpc solution on shared hosting’ is closed to new replies.