3 ms·
It could just as easily have gone the other way: a new spec implemented only in one browser (typically Chrome, as it most frequently ships things first, often i
by chrismorgan 2y ago
It could just as easily have gone the other way: a new spec implemented only in one browser (typically Chrome, as it most frequently ships things first, often incomplete) and, badly implemented by a server, causing such a problem.
- swiftcoder 2y agoI mean, that's pretty much how we got HTTP/2 Push as a standard in the first place, so it's somewhat fitting we lose it the same way.