Really simple SSL ProAutomatically detects your settings and configures your website to run over https.
The parameters are minimized for convenience. The entire site will switch to SSL.
An SSL certificate for a website, what is it and why do you need it?
When you click on a link in your browser (internet access program), you may notice that some web pages look like: "https://freewp.io" and some "https://freewp.io"
fornon-SSLThe version data is passed to the user over an insecure channel, the second version - on the other hand - the information is transmitted over a secure and encrypted channel (SSL).
The first option is for small Internet projects, such as blogs, small online stores, corporate information sites.The latter are used for large portals and large Internet resources or large commercial directories.
⭐ Maybe you are interestedFree Premium WordPress Plugin. Try it now!
Advanced Features Really Simple SSL Pro
- Extensive scanning allows you to use the Repair button to detect mixed content sources that cannot be corrected automatically
- Premium Email Support
- httpOnly makes cookies secure/encrypted
- Improve security by enabling HTTP Strict Transport Security for your site
- Submit your website toHSTS 预载 list
- Easy-to-enforce security headers: X-Content-Type-Options, X-XSS-Protection, X-Frame-Options, Expect-CT, Certificate Transparency, No Referer when downgrading headers, Content Security Policy, Upgrading Unsafe Requests .
Changelog Really Simple SSL Pro Invalid Free
= v5.3.0 = * Improvement: add support for report-to in CSP * Improvement: increase CSP display limit = v5.2.4 = * Improvement: feedback on not detected headers = 18.104.22.168 = * Fix: Rest API and pretty permalinks check inverted, causing false positive notification in dashboard about the permalink structure v5.2.2 * Fix: double quotes in php headers causing issues since recent browser updates = 5.2.1 = * Improvement: replaced admin notice on inactivate license * Improvement: move security headers above WP Rocket .htaccess rules to prevent compatibility issues * Improvement: enable auto updates * Improvement: Content Security Policy did not allow for wss:// and ws:// web socket protocol * Improvement: removed trailing slash from rest api * Improvement: added rsssl_pause_after_request_count filter to adjust request count on which CSP pauses * Improvement: fixed some reporting variations = 5.2.0 = * Improvement: changed PHP header option to dropdown * Improvement: remove unnecessary parameter in file scan * Improvement: request header origin sometimes returns null. Changing to 'host' resolves the Content Security Policy reporting API in those cases * Improvement: styling issue on scan UX = v5.1.0 = * Improvement: comment on multisite environments caused layout issue = v5.0 = * Updated translations = v4.1.11 = * Fix: for very long .htaccess files, support form in the plugin gave an invalid response. props Vincent = v4.1.10 = * Fix: typo in reset license key obfuscation * Translations update = v4.1.9 = * Improvement: 'none' or '*' attribute deprecated for Permissions Policy * Improvement: Content Security Policy for unsafe inline * Improvement: Interest Cohort added to permissions policy = v4.1.8 = * Fix: PHP headers were set with quotes, causing issues on some servers. * Fix: When switching from "enforce" to "paused", CSP headers were not removed * Improvement: generalized wrap_header function for more robust header generation * Improvement: disable remove .htaccess headers on activation of PHP headers. = v4.1.7 = * Moved secure cookies to free = 4.1.6 = * Improved WP Engine compatibility * Improved Content Security Policy, added option to revoke result from overview * Lowered Content Security Policy request limit = 4.1.5 = * Fix: set defaults firing even when dependency check not validated * Fix: Constant RSSSL_DOING_CSP not set when running the CSP API = 4.1.4 = * Improvement: Added report-paused mode to Content Security Policy generator. Reporting will now automatically pause after 200 requests to prevent high server load * Improvement: Further restricted access to Content Security Policy generator REST API calls * Fix: Default options won't be reconfigured after plugin deactivation/activation = 4.1.3 = * Made PHP header option available on all configurations * Improvement: wrap example code in comments = 4.1.2 = * Fix: File name in upgrade function = 4.1.1 = * Fix: condition for .htaccess writing in combination with do not edit .htaccess option = 4.1.0 = * New: PHP headers support for all security headers, autodetecting necessity for NGINX. * New: Changed feature policy into permissions policy. = 4.0.5 = * Improvement: 404 redirect check expiration set to one year when test is successful = 4.0.3 = * Fix: network settings link * Fix: multisite hsts preload option not saving * Improvement: License notifications. Differ between remaining activations when current site is activated, and when not. = 4.0.2 = * Improvement: exclude .htaccess from edits outside settings page = 4.0.1 = * Fix: decode license for support ticket * Fix: made some untranslatable strings translatable = 4.0.0 = * New user interface * Fix: transient stored with 'WEEK_IN_SECONDS' as string instead of constant * Improvement: notices dashboard, with dismissable notices * Improvement: improved naming of settings, and instructions * Improvement: new translations * Improvement: new fix options in scan * Fix: scan mixed content detection false positive * Improvement: removal of .htaccess lines and wpconfig lines on deactivation * Fix: CSP generation bug for some types * Fix: is_writable check on secure cookies write * Improvement: do not insert default security headers if SSL not enabled yet = v2.1.24 = * Add env=HTTPS for all apache versions * don't set HSTS in PHP when not on SSL, to prevent issues with hstspreload.org validation = 2.0.17 = * Tested up to WordPress 5.5 * Removed consent API support