Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#1

Post by pickledoyster » Wed, Dec 03, 2025, 6:07 AM UTC

Quad9 DOH HTTP/1.1 Retirement, December 15, 2025
quad9.net

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#2

Post by londons_explore » Wed, Dec 03, 2025, 7:38 AM UTC

I think code to implement http/1.1 in whatever software stack they use would have been shorter than the blog post...

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#3

Post by werdl » Wed, Dec 03, 2025, 8:07 AM UTC

londons_explore wrote: post #2

I think code to implement http/1.1 in whatever software stack they use would have been shorter than the blog post...

probably not - it can be quite poorly defined in places and the edge cases can be very fiddly. by pushing for http/2 it encourages more users to pick it up imo

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#4

Post by stingraycharles » Wed, Dec 03, 2025, 8:11 AM UTC

londons_explore wrote: post #2

I think code to implement http/1.1 in whatever software stack they use would have been shorter than the blog post...

I think you’re severely underestimating the complexity of http/1.1. It’s definitely much simpler than http/2, but it’s a lot of code that needs to be maintained.

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#5

Post by cenamus » Wed, Dec 03, 2025, 8:11 AM UTC

werdl wrote: post #3

londons_explore wrote: post #2

I think code to implement http/1.1 in whatever software stack they use would have been shorter than the blog post...

probably not - it can be quite poorly defined in places and the edge cases can be very fiddly. by pushing for http/2 it encourages more users to pick it up imo

http/2 surely not simpler?

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#6

Post by JoshTriplett » Wed, Dec 03, 2025, 8:18 AM UTC

cenamus wrote: post #5

werdl wrote: post #3

Earlier quoted context omitted.

probably not - it can be quite poorly defined in places and the edge cases can be very fiddly. by pushing for http/2 it encourages more users to pick it up imo

http/2 surely not simpler?

Having to support http/1.1 and http/2 is definitely not simpler.

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#7

Post by dev_l1x_be » Wed, Dec 03, 2025, 8:22 AM UTC

I never understood DOH over DOT. It makes sense if you want to hide DNS lookups so that people cannot block the DNS queries to ad and other scam networks.

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#8

Post by 5d41402abc4b » Wed, Dec 03, 2025, 8:23 AM UTC

HTTP/1.1 is still heavily used in embedded system.

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#9

Post by itopaloglu83 » Wed, Dec 03, 2025, 8:45 AM UTC

dev_l1x_be wrote: post #7

I never understood DOH over DOT. It makes sense if you want to hide DNS lookups so that people cannot block the DNS queries to ad and other scam networks.

DOH prevents malicious network providers from blocking DOT traffic to enforce their own DNS services for “efficiency” reasons.

Most ISPs just want to sell your data and with encrypted client hello and DOH they’re losing visibility into what you’re doing.

Re: Quad9 DOH HTTP/1.1 Retirement, December 15, 2025

#10

Post by junon » Wed, Dec 03, 2025, 8:45 AM UTC

dev_l1x_be wrote: post #7

I never understood DOH over DOT. It makes sense if you want to hide DNS lookups so that people cannot block the DNS queries to ad and other scam networks.

It's both. In oppressive countries (Iran, China, Russia) where all traffic is filtered, DOH is supposed to help keep things concealed, too.