.htaccess redirection not working with IFTTT

  • Resolved cpcusteve

    (@cpcusteve)


    4 years, 8 months ago

    I am experimenting with IFTTT and have found that Really Simple SSL stops the WordPress IFTTT service working if using the “Enable 301 .htaccess redirect” setting. Disabling this setting and using the “Enable WordPress 301 redirection to SSL” setting makes the IFTTT WordPress service work correctly. To make the “Enable 301 .htaccess redirect” work correctly when enabled, I have found that it’s necessary to add a new “Rewrite” condition to the .htaccess to prevent the xmlrpc.php URL sent by IFTTT from being rewritten. The full .htaccess insertion after modification which I find works is as follows.

    # BEGIN rlrssslReallySimpleSSL rsssl_version[3.2.9]
    <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTPS} !=on [NC]
    RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
    # The following condition added to make ifttt connection work
    RewriteCond %{REQUEST_URI} !^/xmlrpc.php
    RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
    </IfModule>
    # END rlrssslReallySimpleSSL

    I hope this makes sense. I also suspect that other services using XML-RPC may well fail for the same reason! Perhaps you could consider adding this to the plugin at some stage in the future?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Mark

    (@markwolters)

    Hi,

    all XMLRPC requests will be excluded by the mixed content fixer by default. It sounds like IFTTT requires the xmlrpc.php file to be available over https://. This could be a configuration issue in IFTTT, perhaps you have to update your site address to https:// in IFTTT so the tool will try to connect to your WordPress xmlrpc.php file over SSL.

    Mark

    Thread Starter cpcusteve

    (@cpcusteve)

    Hi Mark

    I think you’re absolutely right about ifttt only working over http. I tried changing to Https: in ifttp and got nowhere as it strips off the Https tag! As you say, the internal filter in the plugin works just fine and seems to not change xmlrpc.php URL, but if you switch to .htaccess, then the URL gets rewritten with the Https tag and ifttt refuses to connect. Hence the suggested extra Rewrite condition.

    Regards
    Steve

    Plugin Author Mark

    (@markwolters)

    Hi Steve,

    I would assume it must be possible to make ITFFF work over SSL as well. I’d suggest to contact their support about it to see if they know of any solutions. There are applications which use xmlrpc over SSL, so excluding it by default doesn’t seem like the preferred solution.

    Mark

    Thread Starter cpcusteve

    (@cpcusteve)

    Hi Mark

    All my experimentation leads me to the conclusion that IFTTT can’t handle an SSL connection, and I’ve spent hours on it!!, but I do take your point and will inquire with their support as to whether it’s possible.

    Many thanks for your help
    Steve

    Thread Starter cpcusteve

    (@cpcusteve)

    Hi Mark

    As a follow-up to this, I think I’ve finally got some reasonably definitive from Wikipedia, extract as follows. Looks like xml-rpc is a http protocol with https as a “wouldn’t it be nice if….”!!!

    ——————

    In XML-RPC, a client performs an RPC by sending an HTTP request to a server that implements XML-RPC and receives the HTTP response. A call can have multiple parameters and one result. The protocol defines a few data types for the parameters and result. Some of these data types are complex, i.e. nested. For example, you can have a parameter that is an array of five integers.

    The parameters/result structure and the set of data types are meant to mirror those used in common programming languages.

    Identification of clients for authorization purposes can be achieved using popular HTTP security methods. Basic access authentication can be used for identification and authentication.

    The protocol does not allow HTTPS, but it is a common and obvious variation to use HTTPS in place of HTTP.

    ——————-

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘.htaccess redirection not working with IFTTT’ is closed to new replies.