TIL: no major web font provider serves CSS & WOFF files with correct `Content-Length` headers
-
-
Replying to @slightlylate
Wrong length or no length? Length isn't sent for chunked encoding which most use, even for fixed-size static resources.
1 reply 0 retweets 1 like -
Replying to @patmeenan
No length. Do you know why they're using chunked encoding for H/2-served resources?
2 replies 0 retweets 0 likes -
Replying to @slightlylate
H2 is no different. Streams don't necessarily specify a length before-hand. I'm not sure H2 itself even cares about the header if it's there or not.
2 replies 0 retweets 2 likes -
Replying to @patmeenan @slightlylate
For literal files on the server chunked encoding is a bit surprising to me. But I'm not surprised that the dynamically constructed bootstrap CSS for Google Fonts is streaming since Google's app servers default to streaming responses.
2 replies 0 retweets 0 likes -
Replying to @cramforce @slightlylate
With intermediary reverse proxies doing things like brotli encoding as the data streams through it's usually easier to just chunk everything.
2 replies 0 retweets 1 like
Interestingly, Google Fonts seems to mostly do the right stuff, except for the dynamic endpoints, e.g.: https://fonts.googleapis.com/css?family=Lato:400,700,700italic …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.