Htaccess and Curl Question

  • Resolved akaanc

    (@akaanc)


    9 years, 7 months ago

    Hello,

    First of all thank you for this plugin.

    I have a problem with this plugin (probably with my server) and maybe you can show me a way to fix it.

    When I activate the plugin it asks me to edit htaccess, even if i manually edit it still shows the same error. And in debug it gives me that error. “curL UNSUPPORTED PROTOCOL”

    I asked my host about the curl and they said everything seems okay. I checked some forums for this error and there was some posts with curl -V command. It has https in protocols. What would you suggest to me what can be wrong?

    curl -V
    curl 7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2 .3 libidn/1.18 libssh2/1.4.2
    Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
    Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

Viewing 1 replies (of 1 total)
  • Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    9 years, 7 months ago

    The check if the redirect rules are inserted does not use curl, it uses file_get_contents.
    If you manually edit the .htaccess, you have to enable the option “stop editing the .htaccess file”. Then edit the .htaccess. Otherwise the file get’s rewritten with an empty string. See also:
    https://really-simple-ssl.com/knowledge-base/manually-insert-htaccess-redirect-http-to-https/

    After that, refresh the settings page.

    That should fix the .htaccess message.

    The failing curl does not have to be a problem. It is used before migration to SSL, as you already have done, to check the SSL connection. Now, it will use it to check if the mixed content fixer is active, but it does not cause functional issues. You might see a message “mixed content fixer not detected”. But if you search your source for “data-rsssl”, and it’s there, you’re fine.

Viewing 1 replies (of 1 total)

The topic ‘Htaccess and Curl Question’ is closed to new replies.