4 ms·
But as of today it's a mixture of nginx (our own fork since nginx folks won't accept all our patches) Could you elaborate, within the limits that you're allowe
by daenney 10y ago
But as of today it's a mixture of nginx (our own fork since nginx folks won't accept all our patches)
Could you elaborate, within the limits that you're allowed, on the patches that got rejected? I'm curious as to what they were about and why they didn't make it in.
- jgrahamc 10y agoFor example, we support both SPDY and HTTP/2 and will do SPDY if an older client can't do HTTP/2. NGINX guys didn't want that. We tend to publish rejected stuff as patches: https://github.com/cloudflare/sslconfig/tree/master/patches https://github.com/cloudflare/sslconfig/tree/master/patches
- daenney 10y agoAwesome, thanks! I can sort of understand not wanting to maintain the SPDY code but I can see how that would be useful to CF to have. I'm a bit disappointed the chacha20 ones aren't making it in. I'm curious about the Dynamic TLS records patch. Could you or someone else that understands what that's doing elaborate on what's going on?