I noticed that edge storage is returning an incorrect content-type for TTF fonts - application/octet-stream. This makes edge rules such as "font/*" ineffective. There are unfortunately still use-cases for ttf.
#Edge Storage: TTF Should Have Correct Mime Type (font/ttf)
worldly folio
charred snow
+1 can confirm, I use .ttf as well as .eot, .woff and .woff2, this should be added.
fathom marsh
I see, i'll have those fixed internally. If you urgently need a fix you can make an edge rule that sets the correct content-type header.
charred snow
I see, i'll have those fixed internally. If you urgently need a fix you can make...
Hey Sunil, thanks for this, could you also please mention that .js should not be returning application/javascript? This is deprecated. The correct return value is text/javascript.
fathom marsh
I'll take a look with the team for that as well.
charred snow
charred snow
Hey Sunil, thanks for this, could you also please mention that .js should not be...
Per IETF RFC 9239 text/javascript is now standard and application/javascript is now considered obsolete
charred snow
I see, i'll have those fixed internally. If you urgently need a fix you can make...
Thank you for the recommendation! I will do this now.
charred snow
I see, i'll have those fixed internally. If you urgently need a fix you can make...
^ Can confirm this will work! @worldly folio
worldly folio
^ Can confirm this will work! <@153730010790887424>
I'm actually using the headers to apply edge rules with đ (caching headers)
I've had to hard code handling the .tff extension for now.
charred snow
I'm actually using the headers to apply edge rules with đ (caching headers)
I'...
Ah right.
I was also going to suggest setting type="font/ttf" and preloading the font to avoid issues but I see.
worldly folio
I'll take a look with the team for that as well.
It might be a breaking change for some (at least for me), since I'm using the content headers returned by edge storage to figure out caching (to reduce the number of edge rules involved). Not a big deal, but it would be nice for a heads up so the rules can be adjusted.
charred snow
I always define the content type personally, to avoid MIME sniffing.
charred snow
It might be a breaking change for some (at least for me), since I'm using the co...
Ah okay.
worldly folio
I always define the content type personally, to avoid MIME sniffing.
Yeah, same, sniffing is disabled by header policy. It's not a big deal since the TTF font's in my use-case are to generate PDF's client side (not even used for the DOM), everything else is using WOFF2 variable fonts - thankfully baseline now.