Author: Leon Wimmenhoeve
Why every site should use SSL
Thinking about moving to SSL, but still having doubts whether it is really necessary? The short answer is Yes. These days, SSL is not just a best practice; but an absolute necessity for websites to ensure secure data transmission between the browser & server. In the past, the difference in performance/load times between HTTP and HTTPS was often mentioned as a contributing factor in delaying the move to SSL. But as SSL/TLS protocols became much more efficient over time, the
Complianz GDPR free WordPress plugin
The last months we have been working hard on our full service GDPR plugin for WordPress, and yesterday we have released the free version of the Complianz GDPR WordPress plugin. This plugin is meant for website owners with visitors in the European Union, who want to comply with the new GDPR privacy regulations. There are a lot of cookie warning plugins around, and a lot GDPR tools available, but Complianz GDPR provides the website owner not only with a cookie
Is your website GDPR compliant?
With the upcoming stricter privacy laws, GDPR, a lot of website owners are asking themselves if their site is ready for this new law. Right now we’re working on a plugin which will help you get your site ready. Let Complianz handle the GDPR for your website! The Complianz GDPR plugin will generate the required privacy statement, cookie statement and other required documents (like the processing contract) for you based on your website configuration, used cookies, and your answers to
Really Simple SSL and GDPR
As a consequence of the upcoming new privacy regulations, the GDPR, some users have been asking if Really Simple SSL is compliant, or if the plugin or add-ons do any user tracking. Because Really Simple SSL and Really Simple SSL add-ons do not process personal identifiable information the GDPR does not apply to these plugins or usage of these plugins on your website. If you need a GDPR (EU) or CCPA (US) solution for a privacy policy and cookie policy
htaccess redirect to https may cause redirect to 401.shtml when using password protection
When using the .htaccess for password protection in combination with the .htaccess 301 redirect to https in Really Simple SSL, a redirect to https://domain.com/401.shtml might occur. A simple solution that has been reported to work is to add ErrorDocument 401 default To the top of your .htaccess, so the end result looks like this (the error document should come before the password lines): # Error Document ErrorDocument 401 default #password protection AuthType Basic AuthName “YOUR AUTH NAME” AuthUserFile “/path/to/file” require