2d9121fa22
We previously added HTTP request method based matching for declarativeNetRequest rules, but non-HTTP(s) requests were treated as having the GET request method. With this change, we instead consider non-HTTP(s) requests to have a special NON_HTTP request method. The result is that rules with a requestMethods condition will no longer match non-HTTP(s) requests. Rules with an excludedRequestMethods condition will continue to match non-HTTP(s) requests, even if every HTTP request method is excluded. Bug: 1013583 Change-Id: Ib140894cba86e7fd59861fe2594c2b449ae4fdeb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2940865 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by: Charlie Harrison <csharrison@chromium.org> Reviewed-by: Karan Bhatia <karandeepb@chromium.org> Reviewed-by: Kelvin Jiang <kelvinjiang@chromium.org> Cr-Commit-Position: refs/heads/master@{#893014}
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: