0 Members and 1 Guest are viewing this topic.
Yeah... I'm afraid I don't know the difference.
I thought only financial sites or shopping sites could/needed to use https?
Plain HTTP is not only vulnerable to sniffing attacks, but also session hijacking, where some attacker grabs your session credentials and is capable of impersonating you to the site in question. Think of what would happen if someone did that to a social networking account (which E is pretty close to being actually). There are ways of mitigating this without using HTTPS but HTTPS is the easiest solution and solves plenty of other security issues besides.
Rather straightforward question for everyone, but some complaints members have had over the past year have been extremely suspicious, so I've been thinking of doing this.
Any time \o/The OP suggested that https would automatically be used on elliquiy.com instead of http - therefore the https everywhere add-on would not be needed. For those using https-everywhere, the https rule given in the code block tells the add-on specifically how to handle pages from elliquiy. ( effectively, to always replace http with https in the url ).Now that you have https anywhere installed ( assuming you have also restarted your browser after installing), your browser will attempt to connect to all websites using https first, then http if https is not available. More accurate details should be available on the link I posted previously.
Page created in 0.085 seconds with 19 queries.