These users are very computer illiterate: and are very likely to freak out from seeing HTTPS "insecurity" errors (especially the way Firefox 3 and Internet Explorer 7 handle it nowadays: FULL STOP, kind of thankfully, but not helping me here LOL). Unfortunately, I can't just switch this around at the client level. However, I know that if my production server goes down, then DNS forwarding kicks in and those clients which have "https" on their shortcut will be staring at (which doesn't work) and a big fat Internet Explorer 7 red screen of uneasyness for my company. On my client's desktops I have SOME shortcuts which point to and (both work). I have a server on HTTPS for which I paid an SSL certification for and a mirror for which I haven't and keep around for just for emergencies so it doesn't merit getting a certification for.
That is, the opposite of what (seemingly) everyone teaches.
0 kommentar(er)
