4 ms·

No. I think the HTTPS in the browser prompts a user to think there is confidential information being passed when your just browsing, so now your break user expe

No. I think the HTTPS in the browser prompts a user to think there is confidential information being passed when your just browsing, so now your break user experience. The app portion could be, and should be for any semi-secret information, but keep the front-end clear of it. Plus any and all external resources in-page must be https, it might hang you or a designer up down the road and break your cert.

HerraBRE 16y ago
I disagree. I might not spring for an EV cert in most cases, but using basic encryption to protect against casual eavesdropping should be the rule, not the exception.
- rubyskills 16y ago
  I'm on this boat too. It irritates me that facebook is pretty wishy washy about which urls they decide to encrypt and which they don't...
- mattgaidica 16y ago
  I am 100% with that mentality, I guess I just see the overhead and understanding of HTTPS causing more problems in practice than solutions for developers who are not security-centric. Think we'll ever see google.com go to SSL?
rubyskills 16y ago
Very good points! It's very interesting to me that when SSL opens up, you immediately feel like confidential information information is going to be passed (which is usually the case).. I didn't think about that before! The app portion is def. protected by SSL and switches to that context when you hit the login path. Your last point is interesting too, as we do pull in external resources such as google fonts, jquery (google's CDN), analytics, etc. but have managed to find an SSL version of those URL's too (luckily). I do see this becoming painful for designers moving forward though when they're trying to pull in external resources that lack support for https url's. All very good points. Do you think the average user notices the SSL activation bar?
- mattgaidica 16y ago
  Yea, luckily nearly every major API and service (Amazon, Facebook, Google..) has an encrypted version to pull from. So as long as the entire team understands that, then I only have the usability issue as an argument. If we could get GoDaddy and other hosts to have like a $10 "Add SSL" feature, I think we would see a really good adoption of it being the standard!

HerraBRE 16y ago

I disagree. I might not spring for an EV cert in most cases, but using basic encryption to protect against casual eavesdropping should be the rule, not the exception.

rubyskills 16y ago
I'm on this boat too. It irritates me that facebook is pretty wishy washy about which urls they decide to encrypt and which they don't...
mattgaidica 16y ago
I am 100% with that mentality, I guess I just see the overhead and understanding of HTTPS causing more problems in practice than solutions for developers who are not security-centric. Think we'll ever see google.com go to SSL?

rubyskills 16y ago

Very good points! It's very interesting to me that when SSL opens up, you immediately feel like confidential information information is going to be passed (which is usually the case).. I didn't think about that before! The app portion is def. protected by SSL and switches to that context when you hit the login path. Your last point is interesting too, as we do pull in external resources such as google fonts, jquery (google's CDN), analytics, etc. but have managed to find an SSL version of those URL's too (luckily). I do see this becoming painful for designers moving forward though when they're trying to pull in external resources that lack support for https url's. All very good points. Do you think the average user notices the SSL activation bar?

mattgaidica 16y ago
Yea, luckily nearly every major API and service (Amazon, Facebook, Google..) has an encrypted version to pull from. So as long as the entire team understands that, then I only have the usability issue as an argument. If we could get GoDaddy and other hosts to have like a $10 "Add SSL" feature, I think we would see a really good adoption of it being the standard!