No, I'm not. I'm just explaining why the HTTPS connection is refused (and should be refused, as the whole point of HTTPS is security, and the security cannot be ensured in this case).Joel Cairo wrote:So you are in the "https everywhere/http nowhere camp".
Here's an analogy:
Case 1: I meet someone who simply tells me her name is Alice. (Analogous to: The server does not offer HTTPS.)
Case 2: I meet someone who shows me an ID card that has the name "Bob" on it, and earnestly insists that this ID card proves that he/she is Alice. (Analogous to: arboreumco.com tries to identify themselves by showing you herokuapp.com's ID card/certificate.)
I'm more inclined to believe her in case 1 than in case 2. If you think there's nothing suspicious about case 2 and decide to trust her, that's your decision. But the browser has every reason to warn you that something is wrong.
I'm not even sure how security by obscurity would come into play here.Joel Cairo wrote:Possibly you could argue that therefore trusting it is as safe as 'security by obscurity'