In HTTP/1.1 are connections shared across multiple chrome tabs to the same origin?

Question

In HTTP/2, one connection is used per origin.

Why do you have the assumption that http/2 uses one connection that is shared across multiple chrome tabs if they have the same origin? — t.niese, Jul 26 '18 at 14:55
I checked in chrome://net-internals live HTTP2_SESSION by opening two tabs for same website which is on http2. — priyankatanvani, Jul 27 '18 at 07:52

score 2 · Accepted Answer · answered Aug 01 '18 at 06:05

Yes. In Chrome, HTTP/1.1 sockets are stored in a pool when they are not active. A request from any tab may end up using any socket in the pool.

That having been said... Incognito tabs use their own independent socket pool (All incognito tabs for a profile share just one socket pool, though). Isolated apps use their own socket pools. Different profiles and guest mode use their own socket pools. Global requests not tied to a profile use their own socket pool. And there are a couple other socket pools hanging around (Cloud print uses its own, as does safe browsing).

Each socket pool also separates "uncredentialed sockets" from those that use some form of identity (cookies, HTTP auth, etc).

Source: here

In HTTP/1.1 are connections shared across multiple chrome tabs to the same origin?

1 Answers1