- Autor: sanyy, 2 lata temuOcena: 3/5I'm rating the 0.2.6 with * and this one 0.2.9 with 3*.
- settings are saved again
- does not always activate the https version of a site
(automatic rules are disabled, time increased 30s)
Test it with some non-HSTS site like:
- Autor: PeterW, 2 lata temuOcena: 3/5May be useful but it just breaks some sites. I no longer can login into some sites that mix HTTPS and HTTP requests (for example with login and CAPTCHA elements). Needs some improvement.
- Autor: Firefox user 13532519, 3 lata temuOcena: 3/5The extension does what I want but when I come to a website that requires http I click the back to http (add to whitelist) it never works. I can see it in the whitelist that shows when you click "Open settings page" but it still tries to use HTTPS. The url is www.syracuse.com I am running firefox version 57.0 64 bit. I love your addon but it is frustrating that the application is ignoring it's own settings.
- Autor: Korwin, 4 lata temuOcena: 3/5На части постоянно используемых сайтов появляются задержки по 30+ с. После этого таймаута функционал полностью восстанавливается. Непонятен принцип работы черного и белого списков.
- Autor: RicRud, 4 lata temuOcena: 3/5Dear sir, we have been waiting for you at GitHub to merge pull request.
Are you still keen on updating this for Chrome/Opera/Vivaldi?
Please let some of us know? PM me if you will. We want to see this being updated and developed for Opera/Vivaldi/Chrome too. Please let us know if you want to pass the Git on... --- ,,, But we hope that if you could keep maintaining, but also we understand if not convenient for you at this time.
- Autor: Firefox user 12659481, 4 lata temuOcena: 3/5For some time the addon does not revert back to the HTTP address, it just shows an error message. Maybe a problem in combination with ublock origin and umatrix.
- Autor: Felix, 4 lata temuOcena: 3/5Hey,
is this addon compatible with HTTPS Everywhere?
What would happen, if HTTPS Everywhere normally would bypass to a special https-Site, for example http://www.google.com -to https://encrypted.google.com, but there is no simple https-Variant of that site (like http://aaa.xx to https://aaa.xx)?
Would smart https reject bypassing to the special https-Site?