Conversation
review · 1 starsNot only does this not work – YOU CANNOT DISABLE OR REMOVE HSTS after this plugin! I can’t access my website anymore, because this ‘author’ made it impossible to remove or disable hsts – I disabled and removed the plugin, cleared cache, rebooted the server – HSTS is still on!!!!!!
Firstly the etiquette is to ask for support first Before giving a bad review. Especially as the behaviour you mention is precisely what HSTS is supposed to do, ie prevent visitors accessing your site using downgraded protocols: https://en.m.wikipedia.org/wiki/HTTP_Strict_Transport_Security Once the plugin is inactive though the solution to your ongoing issue is trivial though (and has nothing to do with my plugin and would happen would be the same for every HSTS plugin). You can find instructions here: https://www.ssl2buy.com/wiki/how-to-clear-hsts-settings-on-chrome-firefox-and-ie-browsers Can you please remove your review as it is very unfair?
And you can view my plugin working perfectly on 100s of sites, here is one example: https://boomersclub.com.au/ This reply was modified 5 years, 4 months ago by shawfactor . This reply was modified 5 years, 4 months ago by shawfactor .
@xorred In few words: once you enable HSTS, by using plugin or setting header in webserver config (.htaccess), visitors browser remembers it and will use even if HSTS header is not supplied anymore (plugin disabled). The only way to reenable HTTP access is to “forget about this site” in every visitor browser (that is nearly impossible to do if you have many visitors). So you have to be very careful before you decide to enable HSTS. Maybe plugin author needs an explantation in plugin readme and the plugin itself for less techie people. Well, this is not a support topic, anyway 🙂
@fierevere Unfortubately it i not really a fair review either. This sort of thing so frustrating for good plugin authors
Firstly the etiquette is to ask for support first Before giving a bad review. Especially as the behaviour you mention is precisely what HSTS is supposed to do, ie prevent visitors accessing your site using downgraded protocols: https://en.m.wikipedia.org/wiki/HTTP_Strict_Transport_Security Once the plugin is inactive though the solution to your ongoing issue is trivial though (and has nothing to do with my plugin and would happen would be the same for every HSTS plugin). You can find instructions here: https://www.ssl2buy.com/wiki/how-to-clear-hsts-settings-on-chrome-firefox-and-ie-browsers Can you please remove your review as it is very unfair?
And you can view my plugin working perfectly on 100s of sites, here is one example: https://boomersclub.com.au/ This reply was modified 5 years, 4 months ago by shawfactor . This reply was modified 5 years, 4 months ago by shawfactor .
@xorred In few words: once you enable HSTS, by using plugin or setting header in webserver config (.htaccess), visitors browser remembers it and will use even if HSTS header is not supplied anymore (plugin disabled). The only way to reenable HTTP access is to “forget about this site” in every visitor browser (that is nearly impossible to do if you have many visitors). So you have to be very careful before you decide to enable HSTS. Maybe plugin author needs an explantation in plugin readme and the plugin itself for less techie people. Well, this is not a support topic, anyway 🙂
@fierevere Unfortubately it i not really a fair review either. This sort of thing so frustrating for good plugin authors