Re: [whatwg/fetch] Pass in content type to resource-timing (PR #1481)

> It also seems like we need to have [w3c/server-timing#89](https://github.com/w3c/server-timing/issues/89) resolved before continuing here.

@annevk the equivalent concerns related to this are currently handled in the [ResourceTiming PR](https://github.com/w3c/resource-timing/pull/341/files#diff-0eb547304658805aad788d320f10bf1f292797b5e6d745a3bf617584da017051R714), essentially enabling user agents to trim entropy off of mime types to align them with a well-known list.

We tried to go off a [well-known list of types in MIMESNIFF](https://mimesniff.spec.whatwg.org/#mime-type-groups), but there seem to be types that have inherent entropy in their essence ("+zip" and "+xml" types specifically) which made that unreasonably hard.

So, I guess the open questions are:
a) Is implementation-defined trimming good enough from your perspective? Given that the concern doesn't have consensus around it, I thought this would be good enough.
b) Do you prefer the trimming to happen in Fetch rather than in RT?

/cc @achristensen07

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1481#issuecomment-1259058653
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1481/c1259058653@github.com>