Tag feed

#http2

87 posts25 followers

Explore Hashnode

Alternatives

Trending tags this week

ASAbhijeet Shindeweeklyupdate.hashnode.devSep 5 · 10 min read

How HTTP Works: What Happens After DNS Hands You an IP

1. Why This Topic Matters The last post ended on a promise: once DNS resolves a name to an IP, what actually happens next? Every post in this series up to now — TCP, UDP, and finally DNS — has been ab

0

BSBikash Shawbackendblogs.hashnode.devAug 21 · 12 min read

Computer Networks #13: HTTP/2: How HTTP Became Faster

In the previous blog, we looked at HTTP/1.1 and one of its biggest limitations: Head-of-Line Blocking. HTTP/1.1 allowed us to reuse the same TCP connection for multiple requests, but it still had limi

0

ASAnik Sikderaniksikder.hashnode.devAug 1 · 8 min read

Multiplexing vs Connection Pooling: Why HTTP/2 Changed Everything

In the previous articles of this series, we explored a recurring theme: Every generation of web infrastructure solved one bottleneck only to expose another. HTTP/1.0 suffered from connection setup ov

0

OFOluwaseyi Fatunmolefreecodecamp.orgJul 23 · 50 min read

How Clients and Servers Communicate: Full Handbook on HTTP/1.1, HTTP/2, REST, WebSockets, GraphQL, gRPC, and Protocol Buffers

You've built and consumed APIs. You know what a GET request is, what a JSON response looks like, and how to add an Authorization header. You've used REST, maybe tried GraphQL, and perhaps heard of gRP

0

VKVignesH KumaRhappyvig.hashnode.devJul 9 · 13 min read

HTTP 103 Early Hints, Explained the Way I Wish Someone Had Explained It to Me

🔍 How I got here I came across HTTP 103 Early Hints while reading about how larger sites shave milliseconds off their load times. The idea is elegant enough to stop and think about: a server usually

0

RCRahul Chaduvulasoftwareconcepts.hashnode.devMay 30 · 7 min read

Understanding HTTP as a Backend Engineer

After learning about the OSI model, TCP, and UDP, the next thing I wanted to understand was HTTP. As backend engineers, we work with HTTP every day. We build APIs. We send requests. We receive respons

0

DSDoogal Simpsondoogal.devMar 28 · 5 min read

What About Second HTTP? Solving the 100-File Connection Bottleneck

TL;DR: HTTP/2 replaces the inefficient six-connection limit of HTTP/1.1 with a single, multiplexed stream. By breaking assets into small, interleaved chunks, it eliminates head-of-line blocking and pr

0

OOOluwatomisin Omotoshooluwatomisin-omotosho.hashnode.devMar 27 · 9 min read

gRPC vs REST in Production

The System That Was Working, until It Wasn't When we started building the backend for a telehealth platform, REST was the obvious choice. We had a handful of services like patient records, scheduling,

0

TITech Insights Hubtopperblog.hashnode.devFeb 12 · 9 min read

HTTP/2 Server Push: Performance Optimization

Why Traditional Server Push Strategies Fail in Modern Environments The original Server Push specification assumed a simpler web architecture. In 2025, several factors make naive implementations problematic: Cache complexity across edge networks: Mode...

0

DCDaniele Crucianidanielecr.hashnode.devDec 11, 2025 · 6 min read

Use SNI for routing https requests

The scenario is a proxy exposing https protocol. SNI, Server Name Indication, happens before ssl handshake negotiation. If SNI is used for routing https request, the same port can be used for multiple domains The problem is on passing the headers: X...

0

#http2

Search Hashnode

#http2

Explore Hashnode

Trending tags this week

How HTTP Works: What Happens After DNS Hands You an IP

Computer Networks #13: HTTP/2: How HTTP Became Faster

Multiplexing vs Connection Pooling: Why HTTP/2 Changed Everything

How Clients and Servers Communicate: Full Handbook on HTTP/1.1, HTTP/2, REST, WebSockets, GraphQL, gRPC, and Protocol Buffers

HTTP 103 Early Hints, Explained the Way I Wish Someone Had Explained It to Me

Understanding HTTP as a Backend Engineer

What About Second HTTP? Solving the 100-File Connection Bottleneck

gRPC vs REST in Production

HTTP/2 Server Push: Performance Optimization

Use SNI for routing https requests