CloudFlare enables Websockets for all accounts
-
https://support.cloudflare.com/hc/en-us/articles/200169466-Can-I-use-CloudFlare-with-WebSockets-
@Minion-Queen tell @scottalanmiller to quit making f[moderated]ing excuses.
Enable SSL.
-
There's a way to say everything:
- the fluffy management way (more buzz words than a bee hive)
- the to the point way (condensed but polite)
- the sugar coated way (not recommended for those on diets)
- the @JaredBusch freight-train-to-the-face way
-
+1 for SSL
-
Appears to be working.
-
SSL for the win. I switched and it's working.
-
@nadnerB said in CloudFlare enables Websockets for all accounts:
There's a way to say everything:
- the fluffy management way (more buzz words than a bee hive)
- the to the point way (condensed but polite)
- the sugar coated way (not recommended for those on diets)
- the @JaredBusch freight-train-to-the-face way
This has been asked politely for a LONG time.
-
@scottalanmiller said in CloudFlare enables Websockets for all accounts:
Appears to be working.
Looks goodish.
-
Working here for me too!
Looks like the image tags need to be dynamic or whatever, so that when using https on the site, the ads also use https.
-
That's a lot more complex as the images can be from anywhere. Any across the board change would break some of them.
-
Why don't we redirect HTTP to HTTPs?
-
@Jason said in CloudFlare enables Websockets for all accounts:
Why don't we redirect HTTP to HTTPs?
Because excuses.
-
@JaredBusch said in CloudFlare enables Websockets for all accounts:
@Jason said in CloudFlare enables Websockets for all accounts:
Why don't we redirect HTTP to HTTPs?
Because excuses.
Hardly. Because we don't want people getting hit with the performance penalty who don't want it. There is no reason to redirect it. Everyone can choose what they want.
-
@scottalanmiller said in CloudFlare enables Websockets for all accounts:
@JaredBusch said in CloudFlare enables Websockets for all accounts:
@Jason said in CloudFlare enables Websockets for all accounts:
Why don't we redirect HTTP to HTTPs?
Because excuses.
Hardly. Because we don't want people getting hit with the performance penalty who don't want it. There is no reason to redirect it. Everyone can choose what they want.
As I stated, excuses.
You ALWAYS claim this. There is no performance hit that users should ever notice. You simply need to possibly allocate more CPU. It is you choosing to not do it.
-
Don't mind me...
-
@scottalanmiller said in CloudFlare enables Websockets for all accounts:
That's a lot more complex as the images can be from anywhere. Any across the board change would break some of them.
But you could at least fix all of your stuff to be SSL and at least the landing page will show green, unlike now. There is no content here that is out of your control.
-
@JaredBusch said in CloudFlare enables Websockets for all accounts:
@scottalanmiller said in CloudFlare enables Websockets for all accounts:
@JaredBusch said in CloudFlare enables Websockets for all accounts:
@Jason said in CloudFlare enables Websockets for all accounts:
Why don't we redirect HTTP to HTTPs?
Because excuses.
Hardly. Because we don't want people getting hit with the performance penalty who don't want it. There is no reason to redirect it. Everyone can choose what they want.
As I stated, excuses.
You ALWAYS claim this. There is no performance hit that users should ever notice. You simply need to possibly allocate more CPU. It is you choosing to not do it.
It's the reason. Call it an excuse all you want. You have the feature that you wanted, what's the excuse for requesting redirection other than to complain? You are complaining that we give people choices? Why?
-
@scottalanmiller said in CloudFlare enables Websockets for all accounts:
@JaredBusch said in CloudFlare enables Websockets for all accounts:
@scottalanmiller said in CloudFlare enables Websockets for all accounts:
@JaredBusch said in CloudFlare enables Websockets for all accounts:
@Jason said in CloudFlare enables Websockets for all accounts:
Why don't we redirect HTTP to HTTPs?
Because excuses.
Hardly. Because we don't want people getting hit with the performance penalty who don't want it. There is no reason to redirect it. Everyone can choose what they want.
As I stated, excuses.
You ALWAYS claim this. There is no performance hit that users should ever notice. You simply need to possibly allocate more CPU. It is you choosing to not do it.
It's the reason. Call it an excuse all you want. You have the feature that you wanted, what's the excuse for requesting redirection other than to complain? You are complaining that we give people choices? Why?
Excuses. I have read on this subject ever since you first started using the excuse, because I have never heard anyone prove it to actually be impactful today.
https://www.maxcdn.com/blog/ssl-performance-myth/
http://scn.sap.com/community/netweaver/blog/2013/06/23/whos-afraid-of-ssl -
We know that SSL does in fact add latency to connections.
From that article
"What began as an optional account setting two years earlier became the default for all of Facebook’s 1 billion plus users. Facebook recognized that SSL’s extra round trips could cause delays for some users, but two techniques helped them minimize and – in many cases – eliminate the extra latency."So currently, for HTTPs on Mango it's optional because they don't want to slow down users by milliseconds. That's their choice, The same way as it's Unitrends choice not to SSL their contact forms. So many big companies are still not using HTTPs on their sites.
http://www.unitrends.com/company/contact
The demand for HTTPs clearly is not there from IT pros because the vendors of the software they sell to us are not interested in deploying HTTPs.
This is an enjoyable read about SSL and it's not coming from a marketing CDN provider who is telling you to use their product to make HTTPs work.
-
@Breffni-Potter said in CloudFlare enables Websockets for all accounts:
We know that SSL does in fact add latency to connections.
From that article
"What began as an optional account setting two years earlier became the default for all of Facebook’s 1 billion plus users. Facebook recognized that SSL’s extra round trips could cause delays for some users, but two techniques helped them minimize and – in many cases – eliminate the extra latency."So currently, for HTTPs on Mango it's optional because they don't want to slow down users by milliseconds. That's their choice, The same way as it's Unitrends choice not to SSL their contact forms. So many big companies are still not using HTTPs on their sites.
http://www.unitrends.com/company/contact
The demand for HTTPs clearly is not there from IT pros because the vendors of the software they sell to us are not interested in deploying HTTPs.
This is an enjoyable read about SSL and it's not coming from a marketing CDN provider who is telling you to use their product to make HTTPs work.
Yes, milliseconds. For an online community forum. This is not a Wall Street trading firm.
-
@JaredBusch: Every decision we make here increases costs and also increases issues that we could have. Please remember that we are still very new and trying to bring in as much traffic from Google as possible to grow the community. Which will then interest more vendors which will allow us to spend more on infrastructure and so on.
To be clear not afraid of SSL if there is need. However we also have to remember that it must be used in a way that if fully bennifical for the community as a whole and yes that includes the Google giant and other marketing avenues. In order for this community to continue to grow we need new users and visitors. If we secure everything too much then well........ we wont get that.
