Are connections in HTTP/1.1 shared across multiple chrome tabs to the same origin?

[Priyanka Tanvani]

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

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

[Ryan Hamilton]

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.

Hope that helps!

On Mon, Jul 30, 2018 at 12:49 AM, Priyanka Tanvani <priyank...@gmail.com> wrote:

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

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

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/eda8846d-abfc-42a5-9f9e-d83803588cf8%40chromium.org.

[Matthew Menke]

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).