4aa90bdde1
Expand excludedResponseHeaders to a HeaderCondition so it can exclude
rule matches based on header values as well.
Schema:
{
// the header to exclude if this condition matches. If only this field
// is specified, this condition matches only on the header name.
string header;
// if specified, the rule is not matched if the header contains one
// of these values.
string[]? values;
// if specified, this headercondition is skipped if the header
// contains one of these values. Think of this as an "allowlist"
// for the header where if its value is in this list, the rule *can*
// still match.
string[]? excludedValues;
}
Bug: 1141166
Change-Id: I2e001a4e7ccbd94b917a4b0eeea28fb7e042f72d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5231942
Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1256953}
This will become a reusable extensions module. It implements the core parts of Chrome's extension system, and can be used with any host of the content module.
Some extensions code that is not Chrome-specific still lives in //chrome/browser/extensions and will be moved here.
Technical Documentation: