HTTPS - Page 3

chalsall · 2017-03-22, 19:43

Quote:

Originally Posted by CRGreathouse

I assume it's bog-standard price discrimination, having no connection to costs incurred. But I'm not privy to their internal decision-making processes.

But you are the buyer.

CRGreathouse · 2017-03-22, 21:15

Quote:

Originally Posted by chalsall

But you are the buyer.

I'm not sure what you're getting at.

chalsall · 2017-03-22, 21:39

Quote:

Originally Posted by CRGreathouse

I'm not sure what you're getting at.

I believe in the Latin its "Caveat emptor".

CRGreathouse · 2017-03-23, 00:56

Quote:

Originally Posted by chalsall

I believe in the Latin its "Caveat emptor".

Yes, but I'm not buying their HTTPS.

Since it's just my personal website, I'm happy enough to keep it on HTTP.

Edit: In other words, the price discrimination is working: people like me who don't need SSL get hosting at a cheap price, while people who need it get charged a high price.

ET_ · 2017-03-23, 07:37

Quote:

Originally Posted by CRGreathouse

Edit: In other words, the price discrimination is working: people like me who don't need SSL get hosting at a cheap price, while people who need it get charged a high price.

No. The market laws say "while people who need it get another provider".

CRGreathouse · 2017-03-23, 16:34

Quote:

Originally Posted by ET_

No. The market laws say "while people who need it get another provider".

Maybe, I wouldn't know. I don't know how their prices compare to the others in that market. I apparently feel that for what they offer, their HTTP prices are competitive.

chalsall · 2017-03-23, 21:24

Quote:

Originally Posted by CRGreathouse

Maybe, I wouldn't know. I don't know how their prices compare to the others in that market. I apparently feel that for what they offer, their HTTP prices are competitive.

And that's fine. For those who's websites don't collect passwords or credit card numbers, there is no need to encrypt.

Except... What about a website which involves medical research? Someone researching information about such things could be tagged as a higher risk to an insurer.

The fundamental point I was trying to make was that HTTPS serving does not have to cost more than insecure HTTP serving. Iff you know what your are doing.

CRGreathouse · 2017-03-24, 04:55

Quote:

Originally Posted by chalsall

The fundamental point I was trying to make was that HTTPS serving does not have to cost more than insecure HTTP serving. Iff you know what your are doing.

Agreed. And fundamentally, everyone should be using HTTPS -- it should be the standard, not the exception. But reality is what it is.

yoyo · 2018-02-10, 18:17

Any answer from the admins if HTTPS will be enabled or why not?

VictordeHolland · 2018-02-10, 20:20

This will become relevant soon:

https://arstechnica.com/gadgets/2018...as-not-secure/

From Chrome version 68 onwards Chrome will mark non-https sits as 'not secure'

heliosh · 2018-02-10, 20:55

The label "not secure" isn't so much of a problem than the fact that it indeed is not secure, which it is already today.

It may not be a problem for forum content, but many people share the same login information (password) for different services. And since these information are transmitted plain-text, it can be a problem.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Why is https://www.mersenne.org so damn buggy?	jxsl13	Information & Answers	2	2017-02-22 03:06
https and www etc etc	Uncwilly	Forum Feedback	1	2012-03-12 20:46
https access to www.mersenne.org failed	LLL	PrimeNet	17	2008-12-26 20:34

2018-02-10, 18:17	#31
yoyo Oct 2006 Berlin, Germany 1001101001₂ Posts	Any answer from the admins if HTTPS will be enabled or why not?

2018-02-10, 20:20	#32
VictordeHolland "Victor de Hollander" Aug 2011 the Netherlands 2³·3·7² Posts	This will become relevant soon: https://arstechnica.com/gadgets/2018...as-not-secure/ From Chrome version 68 onwards Chrome will mark non-https sits as 'not secure'

2018-02-10, 20:55	#33
heliosh Oct 2017 ++41 7D₁₆ Posts	The label "not secure" isn't so much of a problem than the fact that it indeed is not secure, which it is already today. It may not be a problem for forum content, but many people share the same login information (password) for different services. And since these information are transmitted plain-text, it can be a problem.