https://bugzilla.wikimedia.org/show_bug.cgi?id=47832
Neil Kandalgaonkar <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #24 from Neil Kandalgaonkar <[email protected]> --- An idea for dealing with China and other cases where HTTPS is blocked - could there be an 'http://insecure.wikipedia.org'? The inverse of the situation we had with 'https://secure.wikipedia.org'. At least the domain name advertises the problem to the user. This is far less slick than a geolocated redirect, but in situations where HTTPS is blocked, I don't see any way to preserve usability and security at the same time. As far as I know, if HTTPS is blocked, we can't redirect them to HTTP, because they won't even reach our server. We could only 'upgrade', by redirecting from HTTP to HTTPS. But by then it's too late; the article they've requested was captured by intermediaries. Maybe with 'insecure.wikipedia.org', savvy users in places like China would learn the trick, or use browser extensions to fix links. Presumably it would be the 'HTTP Everywhere' extension. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
