---
title: "Comment by Ilya Balakin on \"HTTP v/s HTTPS\" | Hashnode"
description: "Thank you for article, it's a great introduction to HTTP/s! Didn't know that HTTPs preferred by search engines but it sound logical. Wanna add a couple of comme"
url: "https://hashnode.com/posts/http-vs-https/67c188274b9c1b1d5e538b95/comment/67c568d15742570ad00da0f3"
---

[Discussion](https://hashnode.com/posts/http-vs-https/67c188274b9c1b1d5e538b95)

Comment [HTTP v/s HTTPS](https://hashnode.com/posts/http-vs-https/67c188274b9c1b1d5e538b95)

[Ilya Balakin](https://hashnode.com/@setupme)

[Mar 3, 2025](https://hashnode.com/posts/http-vs-https/67c188274b9c1b1d5e538b95/comment/67c568d15742570ad00da0f3)

Thank you for article, it's a great introduction to HTTP/s! Didn't know that HTTPs preferred by search engines but it sound logical.

Wanna add a couple of comments based on my experience: – The speed is basically the same. Latest version of TLS is lightning fast and supports TLS session resumption even if TCP connection is dropped. A small research – [keycdn.com/blog/https-performance-overhead.](https://www.keycdn.com/blog/https-performance-overhead.) – HTTPs also allows to verify client identity with client's certificate. Yes, it's a rare case, but it's possible. Might be suitable for back-2-back integrations.

[Jay Kadlag](https://hashnode.com/@devwithjaydotco)

[Mar 3, 2025](https://hashnode.com/posts/http-vs-https/67c188274b9c1b1d5e538b95/comment/67c568d15742570ad00da0f3#reply-67c58dd470d34b017c25fd17)

Thanks for your insights! You’re right—modern TLS is super fast, and session resumption helps keep connections efficient. The KeyCDN article looks interesting; I’ll check it out!

Also, good point about client certificates in HTTPS. While rare, they’re useful for secure API integrations. Appreciate your input!
