: What changes are coming that would reduce the problems assosciated with HTTPS compared to HTTP? I have a web site under development. It is used for surveys but there's an advertising component.
I have a web site under development. It is used for surveys but there's an advertising component. As it is very new I have used almost all the latest technologies. AngularJS, ASP.NET WebAPI 2 etc.
I am consider what I should do about HTTP and HTTPS. I want my site to appear secure and for me it's important that the user might see a lock or even better company name appearing in the browser search bar to emphasis security.
However I understand that with HTTPS there are some drawback such as the time taken to encode. Going forward is it likely that these drawbacks might become less important so that for example in 5 years time HTTPS may become more of a standard rather than exception?
More posts by @XinRu657
1 Comments
Sorted by latest first Latest Oldest Best
Yes use HTTPS everywhere, add a HSTS policy, use only TLS, etc. HTTPS already is "the standard" and it's plenty fast enough with a proper server setup...it's just that most folks don't take the time or wanna spend the money to use it.
If you consider time to encode a drawback, consider the results of the encoding (good encryption) as a drawback too. I realize that was an example, but really, speed is the only thing one can complain about when it comes to HTTPS.
To answer the title question, HTTP2.0::SPDY would reduce the problems with HTTPS. We already have come beyond SSL2/3 into TLS, processing power is moot, and browser/OS support is wide. Mass SPDY support is a last step towards HTTPS everywhere de-facto software.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.