# How Browsers Choose Between HTTPS over TCP and QUIC

DevFeed: [How Browsers Choose Between HTTPS over TCP and QUIC](<https://devfeed.tech/articles/interesting-bootstrapping-https-11194.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/06/bootstrapping-https/>)

Published: 2025-06-03T06:30:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [Web](<https://devfeed.tech/topics/web.md>), [servers](<https://devfeed.tech/topics/servers.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [quic](<https://devfeed.tech/tags/quic.md>), [server](<https://devfeed.tech/tags/server.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [trust](<https://devfeed.tech/tags/trust.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

## AI overview

The article discusses how browsers determine whether a web server supports QUIC and choose between HTTPS over TCP and QUIC. It notes that browser vendors do not trust distributed database data about server capabilities and instead use a happy eyeballs-like protocol.

## Source excerpt

Jan Schaumann published an interesting blog post describing the circuitous journey a browser might take to figure out that it can use QUIC with a web server. Now, if only there were a record in a distributed database telling the browser what the web server supports. Oh, wait... Not surprisingly, browser vendors don't trust that data and have implemented a happy eyeballs-like protocol to decide between HTTPS over TCP and QUIC.