Closed thijskh closed 6 years ago
Nice, Thijs! These requests can be really annoying.
Could you additionally add application/font-woff
? I noticed this type, too.
Moreover there can be often a bunch of application/json
-requests that bloat the trace window. But I think this type may be a bit critically since these requests could be a (desired) response of an web API or something like that. What do you think?
Added application/font-woff
. I think filtering out json is out of scope at least for this option, that tries to filter out things that we are 'sure' to be irrelevant.
Agreed!
Just one other small thing:
Please additionally add application/font-woff2
.
The amount of types to pass is probably smaller than the amount of excludes... Wouldn't it be better to define the passes, and exclude anything else?
I agree that it's very likely that there are more ex- than includes, Tim. But I think Thijs mentioned a very important point: If it's not really certain that a request can be discarded it'd be safer to have it included.
I could very well imagine that'd be fairly annoying if relevant requests would be filtered away due to an application/*
content-type.
On the other hand it'd be hard to safely predict all relevant content-types. Hence I think it'd be a good idea stick with the current exclude-approach and exclude only those request that are safe to exclude.
In that case, we should exclude audio/. video/ www/ and message/ ... IMHO, it's not the end of the world if something legit gets excluded... We can always show it with the button.
I've added application/font-woff2
.
@tvdijen My approach to this issue is quite pragmatic:
The 'filter resources' option now also filters svg images and webfonts.