Why do Web servers allow you to disable QUIC and HTTP/2

preview_player
Показать описание
some web servers allow you to disable QUIC and HTTP/2, but why?

Become a Member on YouTube

🔥 Members Only Content

Support my work on PayPal

🧑‍🏫 Courses I Teach

🏭 Backend Engineering Videos in Order

💾 Database Engineering Videos

🎙️Listen to the Backend Engineering Podcast

Gears and tools used on the Channel (affiliates)

🖼️ Slides and Thumbnail Design
Canva

🎙️ Mic Gear
Shure SM7B Cardioid Dynamic Microphone

Cloudlifter

XLR cables

Focusrite Audio Interface

📷 Camera Gear
Canon M50 Mark II

Micro HDMI to HDMI

Video capture card

AC Wall for constant power

Stay Awesome,
Hussein
Рекомендации по теме
Комментарии
Автор

Much better format with editing out the hesitations and just speaking faster in general. Great video!

Oliver_Saer
Автор

This channel makes me feel John Snow for backend!

alphaNaj
Автор

Honestly, I think in case of turning off HTTP/2 it's mostly for debug tools not understanding the protocol. So they can disable it and debugging an issue.
In case of QUIC & HTTP/3 not being able to handle UDP traffic fast enough is probably the problem. We've optimized TCP so well for HTTP that even for high load DNS TCP can be faster than UDP !

autohmae
Автор

Hey I apologize, this is unrelated.
how can I get my foot in the door in this field with no degree? I cant afford the CompTIA certifications either so it feela like no one will take me seriously.

kellysmith
Автор

What do you mean that HTTP/2 has headers inside or how does it differ in HTTP/1.1

aymanpatel
Автор

how bad must the overhead be, if your business logic is holding up but packetinspection kills your CPU :D

easteregg
Автор

Watch suggestion: Youtube channel: "Ben Eater" did a great video explaining the routing (BGP) and the Internet, using Facebook as an example: "Why was Facebook down for five hours?"

autohmae
Автор

What to do if we re over-saturated fron learning?

rocketleague