Really Simple SSL

Description

Really Simple SSL détecte automatiquement vos réglages et configure votre site web pour fonctionner en HTTPS.
Pour le garder léger, les options sont réduites au minimum. Le site entier sera déplacé vers SSL.

Trois étapes simples pour configurer :

  • Obtenez un certificat SSL (impossible de le faire pour vous, désolé).
  • Activer cette extension
  • Activer SSL en un clic

Sauvegardez toujours avant d’aller ! Si vous n’avez pas encore de politique de sauvegarde, commencez par en avoir un! Pour un instantané, installez duplicator.

Really Simple SSL est également sur GitHub !

Vous appréciez Really Simple SSL ?

Hopefully this plugin save you some hours of work. If you want to support the continuing development of this plugin, you might consider buying the premium, which includes
some cool features.

Fonctionnalités Pro

  • L’analyse de contenu mixé qui vous affiche ce que vous devez faire si vous n’avez pas encore le cadenas vert
  • L’option pour activer HTTP Strict Transport Security
  • L’option de configurer votre site pour la liste de préchargement HSTS
  • Fixateur de contenu mixte pour l’administration
  • Retours plus détaillés sur la page de configuration.
  • Vérirfication d’expiration du certificat : recevez un e-mail lorsque votre certificat SSL est sur le point d’expirer.
  • Support premium

Que fait effectivement l’extension

  • The plugin handles most issues that WordPress has with ssl, like when you’re behind a revers proxy/loadbalancer, or when no headers are passed which WordPress can use to detect SSL.
  • All incoming requests are redirected to https. Default with an internal WordPress redirect, but you can also enable a .htaccess redirect.
  • L’URL du site et l’URL de l’accueil sont remplacées par https.
  • Votre contenu non sécurisé est corrigé en remplaçant toutes les URLs http:// avec https://, exceptés les hyperliens vers d’autres domainss. Dynamiquement, aucun changement de base de données n’est effectué (sauf pour siteurl et homeurl).

contactez-moi pour toutes questions, problèmes, ou suggestions. Plus d’informations à propos de moi ou de mon travail peuvent être trouvées sur mon site web.

Vous souhaitez avoir cette extension dans votre langue ?

Les traductions peuvent facilement être ajoutées ici. Si vous le faites, je peux vous ajouter comme éditeur de traduction pour approuver les traductions.

Captures d’écran

  • Après activation, si SSL a été détecté, vous pouvez activer SSL.
  • Voir votre configuration sur la page des réglages

Installation

Pour installer cette extension :

  1. Faites une sauvegarde !
  2. Installez votre certificat SSL
  3. Télécharger l’extension
  4. Envoyez l’extension dans le répertoire wp-content/plugins,
  5. Allez à « Extensions » dans votre admin WordPress, puis cliquez sur « Activer ».
  6. Vous allez maintenant voir un avis vous demandant d’activer SSL. Cliquez dessus et re-connectez-vous.

FAQ

Instructions d’installation

Pour installer cette extension :

  1. Faites une sauvegarde !
  2. Installez votre certificat SSL
  3. Télécharger l’extension
  4. Envoyez l’extension dans le répertoire wp-content/plugins,
  5. Allez à « Extensions » dans votre admin WordPress, puis cliquez sur « Activer ».
  6. Vous allez maintenant voir un avis vous demandant d’activer SSL. Cliquez dessus et re-connectez-vous.
Base de connaissances

Pour des explications et une documentation plus détaillées sur les boucles de redirection, la désactivation, le contenu mixte, les erreurs, et autres, veuillez chercher dans la documentation

Le fixateur de contenu mixte rend-il mon site plus lent ?

Sur un site où la source se compose d’environ 60.000 caractères, le retard provoqué par le correcteur de contenu mixte est d’environ 0.00188 secondes. Si c’est trop pour vous, corrigez le contenu mixte manuellement et désactivez-le dans les réglages.

Désinstallation de Really Simple SSL

L’extension vérifie votre certificat avant de l’activer, mais si, par exemple, vous avez migré le site vers un environnement non-ssl, vous risquez d’être bloqué dans l’interface d’administration.
Si vous ne pouvez pas désactiver, ne vous contentez pas de supprime simplement le dossier de l’extension pour désinstaller ! Suivez ces instructions.

Problèmes de contenus mixtes

La plupart des problèmes de contenu mixte sont causés par des URLs dans les fichiers CSS ou JS.
Pour obtenir des instructions détaillées sur la façon de trouver le contenu mixte, lisez cet article.

Problèmes de boucles de redirection

Si vous rencontrez des boucles de redirection sur votre site, essayez ces instructions.

L’extension est-elle compatible multisite ?

Yes. There is a dedicated network settings page where you can switch between network activated SSL and per page SSL. In the dedicated pro for multisite plugin, you can override all site settings for SSL on the network level, and can activate and deactivate SSL in the network menu for each site.* Really Simple SSL maintains an extensive knowledge-base at https://www.really-simple-ssl.com.

Avis

Best Plugin Support Ever!!!

Really easy to Set your WP Site with the SSL Certificate. I Strongly recomend it. The PRO Version is awesome too! Best Plugin Support Ever. Extremely fast and Rogier is a very kind person. I give him 10 stars for his service!
Lucas

What a relieve: EXCELLENT Plugin

When someone gives you three steps to install a plugin then you may think twice. But I had to try it. And yes. It was that simple. Very happy. Great stuff. My site is https in three steps.

Just Installed, but Seems Awesome

Added a Let’s Encrypt Certificate through Dreamhost, installed this plugin, enabled SSL, and it just worked. It is indeed really simple.

(Note, I literally just started using it, so perhaps there are unexpected problems that will bubble up. I’ll update the review if they do.)

Saved me a lot of time and it works perfectly

Thank you very much for your plugin. My website only showed http even though I have installed an SSL key. To fix this issue I had to do a lot of reading and it was quite technical. I had many steps to follow to make all my pages show https by default. I did not do that. It was enough to install Really Simple SSL plugin.

Your plugin saved me a lot of time and it works as it promises.

Lire les 271 avis

Contributeurs & développeurs

« Really Simple SSL » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.

Contributeurs

« Really Simple SSL » a été traduit en 7 langues : French, German, Spanish, Dutch, Chinese (Taiwan), Dutch (Belgium), English (UK). Remerciez l’équipe de traduction pour ses contributions.

Traduisez « Really Simple SSL » dans votre langue.

Le développement vous intéresse ?

Parcourez le code ou abonnez vous à l’historique de développement par RSS.

Journal

2.5.20

  • Tweak: constant RSSSL_DISMISS_ACTIVATE_SSL_NOTICE to allow users to hide notices.
  • Tweak: setting to switch the mixed content fixer hook from template_redirect to init.
  • Fix: nag in multisite didn’t dismiss properly

2.5.19

  • Multisite fix: due to a merge admin_url and site_url filters were dropped, re-added them
  • Added constant RSSSL_CONTENT_FIXER_ON_INIT so users can keep on using the init hook for the mixed content fixer.

2.5.18

  • Tweak: Removed JetPack fix, as it is now incorporated in JetPack.
  • Tweak: Moved mixed content fixer hook to template_redirect
  • Fix: Changed flush rewrite rules hook from admin_init to shutdown, on activation of SSL.
  • Multisite fix: Changed function which checks if admin_url and site_url should return http or https to check for https in home_url.
  • Tweak: Explicitly excluded json and xmlrpc requests from the mixed content fixer

2.5.17

  • Tweak: Added a function where the home_url and site_url on multisite check if it should be http or https when SSL is enabled on a per site basis.
  • Tweak: Added a notice that there will be no network menu when Really Simple SSL is activated per site.
  • Tweak: Added hook for new multisite site so a new site will be activated as SSL when network wide is activated.
  • Tweak: limited the JetPack listen on port 80 tweak to reverse proxy servers.
  • Tweak: created a dedicated rest api redirect constant in case users want to prevent the rest api from redirecting to https.
  • Fix: dismissal of SSL activated notice on multisite did not work properly

2.5.16

  • Reverted wp_safe_redirect to wp_redirect, as wp_safe_redirect causes a redirect to wp-login.php even when the primary url is domain.com and request url www.domain.com

2.5.15

  • No functional changes, version change because WordPress was not processing the version update

2.5.14

  • Fix: fixed issue in the mixed content fixer where on optimized html the match would match across elements.
  • replaced wp_redirect with wp_safe_redirect
  • Added force SSL on wp_rest_api

2.5.13

  • Tweak: configuration more function

2.5.12

  • Added multisite settings page
  • Added filter for .htaccess code output
  • Increased user capability to « activate_plugins »
  • Added SSL_FORWARDED_PROTO = 1 in addition to SSL_FORWARDED_PROTO = on as supported SSL recognition variable.

2.5.11

  • Removed curl in favor of wp_remote_get

2.5.10

  • Fastest cache compatibility fix

2.5.9

  • Multisite tweaks

2.5.8

  • Removed automatic insertion of .htaccess redirects. The .htaccess redirects work fine for most people, but can cause issues in some edge cases.
  • Added option to explicitly insert .htaccess redirect
  • Added safe mode constant RSSSL_SAFE_MODE to enable activating in a minimized way
  • Fix: RLRSSSL_DO_NOT_EDIT_HTACCESS constant did not override setting correctly when setting was used before.
  • Dropped cache flushing on activation, as this does not always work as expected

2.5.7

  • Tweak: changes testurl to the function test_url()

2.5.6

  • version nr fix

2.5.5

  • Reverted some changes to 2.4.3, as it was causing issues for some users.

2.5.4

fix: Adjusted selection order of .htaccess rules, preventing redirect loops

2.5.3

  • Changed .htaccess redirects to use only one condition

2.5.2

  • removed file_get_contents function from class_url.php, as in some cases this causes issues.

2.5.1

  • Added help tooltips
  • Fix: typos in explanations
  • Added detected server to debug Log
  • Added test folder for CloudFlare
  • Added htaccess redirect to use all available server vars for checking SSL.

2.5.0

  • Tweak: Improved support for cloudflare
  • Tweak: Added support for Cloudfront, thanks to Sharif Alexandre
  • Fix: Prevent writing of empty .htaccess redirect
  • Tweak: Added option for 301 internal wp redirect
  • Tweak: Improved NGINX support
  • Tweak: Added support for when only the $_ENV[HTTPS] variable is present
  • Fix: Mixed content fixing of escaped URLS

2.4.3

  • Bannière supprimée en admin

2.4.2

  • Tweak: Added reload over https link for when SSL was not detected
  • Fixed: After reloading page when the .htaccess message shows, .htaccess is now rewritten.
  • Ajustement : avertissements YOAST supprimés
  • Testé pour WP 4.7
  • Correction : bug dans lequel les options réseau n’étaient pas supprimées correctement lors de la désactivation
  • Ajustement : changé le marqueur de contenu mixte à la variation sans guillemets, pour éviter les problèmes avec les scripts, etc.

2.4.1

  • Tweak: improved HSTS check

2.4.0

  • Fixed: added a version check on wp_get_sites / get_sites to get rid of deprecated function notice, and keep backward compatibility.
  • Fixed: A bug in multisite where plugin_url returned a malformed url in case of main site containing a trailing slash, and subsite not. Thanks to @gahapati for reporting this bug.
  • Tweak: Added button to settings page to enable SSL, for cases where another plugin is blocking admin notices.
  • Tweak: Rebuilt the mixed content fixer, for better compatibility
  • Tweak: Improved the mixed content marker on the front-end, so it’s less noticeable, and won’t get removed by minification code.

2.3.14

  • Fixed: Clearing of WP Rocket cache after SSL activation causing an error
  • Fixed: Clearing of W3TC after SSL activation did not function properly

2.3.13

  • Re-inserted Jetpack fix.

2.3.12

  • Requires at least changed back to 4.2, as the function that this was meant for didn’t make it in current release yet.

2.3.11

  • Improved request method in url class
  • Added check if .htaccess actually exists in htaccess_contains_redirect_rules()
  • Rendu le message d’activation plus clair.

2.3.10

  • Testée pour 4.6
  • Tweak: changed check for htaccess redirect from checking the RSSSL comments to checking the redirect rule itself
  • Fix: htaccess not writable message not shown anymore when SSL not yet enabled
  • Tweak: extended mixed content fixer to cover actions in forms, as those should also be http in case of external urls.
  • Tweak: added safe domain list for domains that get found but are no threat.
  • Tweak: added filter for get_admin_url in multisite situations, where WP always returns an https url, although the site might not be on SSL
  • Tweak: htaccess files and wpconfig are rewritten when the settings page is loaded

2.3.9

  • Fix: removed internal WordPress redirect as it causes issues for some users.
  • Tweak: improved url request method

2.3.8

  • Tweak: Fallback redirect changed into internal wp redirect, which is faster
  • Tweak: When no .htaccess rules are detected, redirect option is enabled automatically
  • Tweak: Url request falls back to file_get_contents when curl does not give a result

2.3.7

  • Updated screenshots

2.3.6

  • Fixed: missing priority in template_include hook caused not activating mixed content fixer in some themes

2.3.5

  • Fixed: javascript redirect insertion

2.3.4

  • Tweak: load css stylesheet only on options page and before enabling ssl
  • Tweak: mixed content fixer triggered by is_ssl(), which prevents fixing content on http.
  • Start detection and configuration only for users with « manage_options » capability

2.3.3

  • Fixed bug in force-deactivate script

2.3.2

  • Changed SSL detection so test page is only needed when not currently on SSL.
  • Correction de quelques bugs mineurs.

2.3.1

  • Removed « activate ssl » option when no ssl is detected.
  • Optimized emptying of cache
  • Fixed some bugs in deactivation and activation of multisite

2.3.0

  • Given more control over activation process by explicity asking to enable SSL.
  • Ajouté un avertissement si le fichier .htaccess n’est pas inscriptible

2.2.20

Correction d’un bug dans la détection SSL

2.2.19

Changed followlocation in curl to an alternative method, as this gives issues when safemode or open_basedir is enabled.
Added dismissable message when redirects cannot be inserted in the .htaccess

2.2.18

Fixed bug in logging of curl detection

2.2.17

Corrections de sécurité dans ssl-test-page.php

2.2.16

Bugfix with of insecure content fixer.

2.2.13

Added a check if the mixed content fixer is functioning on the front end
Fixed a bug where multisite per_site_activation variable wasn’t stored networkwide
Added clearing of wp_rocket cache thans to Greg for suggesting this
Added filter so you can remove the really simple ssl comment
Fixed a bug in the output buffer usage, which resolves several issues.
Added code so JetPack will run smoothly on SSL as well, thanks to Konstantin for suggesting this

2.2.12

  • To prevent lockouts, it is no longer possible to activate plugin when wp-config.php is not writable. In case of loadbalancers, activating ssl without adding the necessary fix in the wp-config would cause a redirect loop which would lock you out of the admin.
  • Moved redirect above the wordpress rewrite rules in the htaccess.
  • Added an option to disable the fallback javascript redirection to https.

2.2.11

Brand new content fixer, which fixes all links on in the source of your website.

2.2.10

  • Roll back of mixed content fixer.

2.2.9

Improved the mixed content fixer. Faster and more effective.

2.2.8

Edited the wpconfig define check to prevent warnings when none are needed.

2.2.7

  • Extended detection of homeurl and siteurl constants in wp-config.php with regex to allow for spaces in code.
  • Changed text domain to make this plugin language packs ready
  • Added 404 detection to ssl detection function, so subdomains can get checked properly on subdomain multisite installs

2.2.6

Added slash in redirect rule
small bugfixes

2.2.3

mise à jour de la documentation

2.2.2

  • Ajout d’un support multisite pour le problème de la variable de serveur https manquante
  • Script de connexion curl amélioré
  • Ajout de la traduction française, merci à Cédric

2.2.1

  • Correction de petits bugs

2.2.0

  • Added per site activation for multisite, but excluded this option for subfolder installs.
  • Added script to easily deactivate the plugin when you are locked out of the wordpress admin.
  • Added support for a situation where no server variables are given which can indicate ssl, which can cause WordPress to generate errors and redirect loops.
  • Removed warning on Woocommerce force ssl after checkout, as only unforce ssl seems to be causing problems
  • Added Russian translation, thanks to xsascha
  • Règles de redirection améliorées dans le .htaccess
  • Added option te disable the plugin from editing the .htaccess in the settings
  • Fixed a bug where multisite would not deactivate correctly
  • Fixed a bug where insecure content scan would not scan custom post types

2.1.18

  • Made woocommerce warning dismissable, as it does not seem to cause issues
  • Fixed a bug caused by WP native plugin_dir_url() returning relative path, resulting in no ssl messages

2.1.17

  • Fixed a bug where example .htaccess rewrite rules weren’t generated correctly
  • Added woocommerce to the plugin conflicts handler, as some settings conflict with this plugin, and are superfluous when you force your site to ssl anyway.
  • Excluded transients from mixed content scan results

2.1.16

  • Fixed a bug where script would fail because curl function was not installed.
  • Added debug messages
  • Improved FAQ, removed typos
  • Replaced screenshots

2.1.15

  • Improved user interface with tabs
  • Changed function to test ssl test page from file_get_contents to curl, as this improves response time, which might prevent « no ssl messages »
  • Extended the mixed content fixer to replace src= »http:// links, as these should always be https on an ssl site.
  • Added an errormessage in case of force rewrite titles in Yoast SEO plugin is used, as this prevents the plugin from fixing mixed content

2.1.14

  • Added support for loadbalancer and is_ssl() returning false: in that case a wp-config fix is needed.
  • Improved performance
  • Added debuggin option, so a trace log can be viewed
  • Fixed a bug where the rlrsssl_replace_url_args filter was not applied correctly.

2.1.13

  • Fixed an issue where in some configurations the replace url filter did not fire

2.1.12

  • Added the force SSL option, in cases where SSL could not be detected for some reason.
  • Added a test to check if the proposed .htaccess rules will work in the current environment.
  • Readded HSTS to the htaccess rules, but now as an option. Adding this should be done only when you are sure you do not want to revert back to http.

2.1.11

  • Improved instructions regarding deinstalling when locked out of back-end

2.1.10

  • Removed HSTS headers, because it is difficult to roll back.

2.1.9

  • Added the possibility to prevent htaccess from being edited, in case of redirect loop.

2.1.7

  • Refined SSL detection
  • Bugfix on deactivation of plugin

2.1.6

  • Fixed an SSL detection issue which could lead to redirect loop

2.1.4

  • Improved redirect rules for .htaccess

2.1.3

  • Now plugin only changes .htaccess when one of three preprogrammed ssl types was recognized.
  • Simplified filter use to add your own urls to replace, see f.a.q.
  • Default javascript redirect when .htaccess redirect does not succeed

2.1.2

  • Fixed bug where number of options with mixed content was not displayed correctly

2.1.1

  • limited the number of files, posts and options that can be show at once in the mixed content scan.

2.1.0

  • Added version control to the .htaccess rules, so the .htaccess gets updated as well.
  • Added detection of loadbalancer and cdn so .htaccess rules can be adapted accordingly. Fixes some redirect loop issues.
  • Added the possibility to disable the auto replace of insecure links
  • Added a scan to scan the website for insecure links
  • Added detection of in wp-config.php defined siteurl and homeurl, which could prevent from successfull url change.
  • Dropped the force ssl option (used when not ssl detected)
  • Thanks to Peter Tak, PTA security for mentioning the owasp security best practice https://www.owasp.org/index.php/HTTP_Strict_Transport_Security in .htaccess,

2.0.7

  • Ajout de la redirection 301 au fichier .htaccess à des fins SEO

2.0.3

  • Fixed some typos in readme
  • added screenshots
  • fixed a bug where on deactivation the https wasn’t removed from siturl and homeurl

2.0.0

  • Added SSL detection by opening a page in the plugin directory over https
  • Added https redirection in .htaccess, when possible
  • Added warnings and messages to improve user experience
  • Added automatic change of siteurl and homeurl to https, to make backend ssl proof.
  • Added caching flush support for WP fastest cache, Zen Cache and W3TC
  • Fixed bug where siteurl was used as url to fix instead of homeurl
  • Fixed issue where url was not replaced on front end, when used url in content is different from home url (e.g. http://www.domain.com as homeurl and http://domain.com in content)
  • Added filter so you can add cdn urls to the replacement script
  • Added googleapis.com/ajax cdn to standard replacement script, as it is often used without https.

1.0.3

  • Améliorations des instructions d’installation