111–120 of 123 posts
> with almost 300,000 services using it across the world The Shodan search given scans headers for all requests. So the vast majority of results are sites using Google Fonts, Maps, etc.
Earlier quoted context omitted.
One thing that drives me off from Caddy is that many features don't compose with each other well. I understand this might be a sacrifice for a simpler user interface, but the composition of declarative-style configurations is always a mess compared to imperative ones like nginx.conf
Thanks for the feedback. (To clarify, nginx's config is also declarative... well, mostly: they got in trouble for mixing declarative and imperative [1].) You'd be surprised what we've been able to accomplish with upgrades to Caddy's configuration in Caddy 2. Its config is technically declarative, but the underlying JSON structure [2] implies a procedural flow, enabling you to compose certain behaviors that almost fee…
> HTTP/2, derived from the now deprecated SPDY protocol, introduced the concept of first-class streams embedded in the same connection.
Was this not done by SCTP?
* https://en.wikipedia.org/wiki/Stream_Control_Transmission_Pr...
It's just that (a) network boxes often block 'unknown' protocols, and (b) web servers/browsers did not bother implementing the protocol.
I hate to be a curmudgeon, but I can't help but think that designing a new service over UDP isn't the best idea. DNS has been fighting off wave after wave of attack vectors, some that realistically cannot even be fixed. Making it immune to these vectors is going to look a lot like a slapped together TCP over UDP...
They tried with SCTP and DCCP.
Earlier quoted context omitted.
Thanks for the feedback. (To clarify, nginx's config is also declarative... well, mostly: they got in trouble for mixing declarative and imperative [1].) You'd be surprised what we've been able to accomplish with upgrades to Caddy's configuration in Caddy 2. Its config is technically declarative, but the underlying JSON structure [2] implies a procedural flow, enabling you to compose certain behaviors that almost fee…
Thank you for the quick reply! Currently our routing needs lots of flexibility, and we are wondering if it's possible to have something similar to OpenResty-style [0] config where builtin directives are Lua functions, and users can handle requests by dispatching them in Lua with a function call. [0]: https://openresty.org/en/
From the article: > HTTP/2, derived from the now deprecated SPDY protocol, introduced the concept of first-class streams embedded in the same connection. Was this not done by SCTP? * https://en.wikipedia.org/wiki/Stream_Control_Transmission_Pr... It's just that (a) network boxes often block 'unknown' protocols, and (b) web servers/browsers did not bother implementing the protocol.
Earlier quoted context omitted.
How does QUIC lead to "less ability to block them"?
I am not sure. But seems like the nature of the encrypted connection and the stream utilisation (akin to HTTP/2) would make it harder for something like e.g. your home PiHole to block ads at the DNS level -- or any other lower-level in your network before stuff hits the browser. I should have worded my comment better. It wasn't a claim, it was more like a "I think Google wants this protocol to succeed for their own u…
Because QIC is UDP based, Chrome first runs a race with TCP just in case you're sitting behind some device that blocks UDP. I wonder how much bandwidth this will waste globally.
Yeah I'm not deploying this, pretty much ever. I'll gladly eat the overhead of TCP to be able to avoid the reflection and spoofing issues of UDP.
The only reason QUIC is built on top of UDP is because ossification prevents it from being built on top of IP. It's essentially at the same level as TCP- and provides similar mechanisms to avoid UDP's issues.
Whitelisting patterns are incredibly common. Breaking that breaks a lot of stuff.
Why are they calling it HTTP/3 and not just keeping the QUIC name?
Something similar happened with SPDY (Google's experiment) and HTTP/2 (IETF standard based on SPDY).