It doesn't make sense to use it for guests but not for members. You want to protect the login credentials and other personal information, which guests do not supply in the first place...
--------------- Added [DATE]1486890492[/DATE] at [TIME]1486890492[/TIME] ---------------
As an afterthought: You're even deluding your potential users. As guests, they see a https-enabled forum. Once they decide to register (and supply personal information), it's all plain open. I'd feel played and would be really pissed.
It's not a good idea to simulate https just for Google's sake.
02-11-2017, 01:08 PM
Threaded Mode