6 ms·
The link still isn't working. But this is not an assumption on my part. It is from experience. At my last startup, we ran the entire most everything over htt
by epi0Bauqu 19y ago
The link still isn't working.
But this is not an assumption on my part. It is from experience. At my last startup, we ran the entire most everything over https because it yielded better sign up numbers and payment conversions (pre-payment page). We had at some points over 50K people signing up daily (and of course many many more hitting the initial sign up page and current users logging in and clicking around). The registration # is to give you an idea of scope. All of this still ran fine one dual CPU machine, i.e. all the https didn't hit the server too hard to where it mattered.
So I guess I'm not disputing https takes a lot more CPU than http, but in the aggregate, with a decent machine, it just isn't going to matter. This is especially true if you just do it for authentication, and yes I was thinking of the same cookie process as described by mdakin when making the original comment.