Bugzilla

Please disregard previous comment.  I wanted to reuse the "initiator" column and though it's fed solely from the `PerformanceResourceTiming.initiatorType` information on the channel.  It's not and values for that attribute are actually [quite limited](https://www.w3.org/TR/resource-timing-1/#dom-performanceresourcetiming-initiatortype).

Hence, we need to discuss how this should be exposed on the channel.  I see following options:
- as we are monitoring only HTTP requests (while preload can be made for any schema!) add a bool property on nsIHttpChannel
- add a property on nsILoadInfo; but loadinfo should only contain stuff related to security, which this is not
- have a new interface nsIPreloadingChannel with the bool property and let channels we want to carry this information implement it

The simplest is the first option and I think sufficient even mid- or long-term.

Please disregard previous comment.  I wanted to reuse the "initiator" column and though it's fed solely from the `PerformanceResourceTiming.initiatorType` information on the channel.  It's not and values for that attribute are actually [quite limited](https://www.w3.org/TR/resource-timing-1/#dom-performanceresourcetiming-initiatortype).

Hence, we need to discuss how this should be exposed on the channel.  I see following options:
- as we are monitoring only HTTP requests (while preload can be made for any schema!) add a bool property on nsIHttpChannel
- add a property on nsILoadInfo; but loadinfo should only contain stuff related to security, which this is not
- have a new interface nsIPreloadingChannel with the bool property and let channels we want to carry this information implement it
- add new CSP internal types for actual link rel=preload requests (for each supported type) and get also the naming right: what is now `PRELOAD` but actually is a speculative load, should be renamed to `SPECULATIVE` and use `PRELOAD` for <link preload> channels

The simplest is the first option (nsIHttpChannel) and I think sufficient even mid- or long-term.  The most correct, but with some work, is the last option (new CSP types).