#http3 use right now:
Firefox beta 121: 28% of all HTTP
w3techs: 29.7% of the top-1M websites
Cloudflare: 30.0% of monitored web traffic
⇧
#http3 use right now:
Firefox beta 121: 28% of all HTTP
w3techs: 29.7% of the top-1M websites
Cloudflare: 30.0% of monitored web traffic
daniel:// stenberg://
in reply to daniel:// stenberg:// • • •Luigi
in reply to daniel:// stenberg:// • • •Stefan Eissing
in reply to daniel:// stenberg:// • • •Teixi
in reply to Stefan Eissing • • •@icing
There's still a long road for most libraries/clients to switch to http/2
Just this week read this craziness:
» Remarks
In .NET Core, the default message version differs based on the version you're using.
.NET Core 2.1 changed the default value from 1.1 to 2.0.
In .NET Core 3.0, the default value was reverted back to 1.1. «
learn.microsoft.com/en-us/dotn…
HttpRequestMessage.Version Property (System.Net.Http)
learn.microsoft.comdaniel:// stenberg://
in reply to Teixi • • •Teixi
in reply to daniel:// stenberg:// • • •Indeed! Plus now I recalled what they did once their sillyShell curl alias os level block link to their poor alternative:
daniel.haxx.se/blog/2016/08/19…
Appl did something alike, but only on their own os when switched from sys8 to OzX. But distinctly aliases goal were for helping customers scripts backwards compatibility...
...can't recall of any other cases of global command line tools anticompetitive unlawful tactics via alternatives alias default os block?
news.ycombinator.com/item?id=1…
Removing the PowerShell curl alias? | daniel.haxx.se
daniel.haxx.seStefan Eissing
in reply to daniel:// stenberg:// • • •The curious thing is that when I try 'fastly.com' or 'google.com' in Firefox or Safari, they do HTTP/2.
But I know that HTTP/3 would work with these sites.
So: are browsers ever trying HTTP/3 on a desktop machine/fixed network?