On Wed, Jun 17, 2015 at 10:31 AM, Sebastian Noack <[email protected] > wrote:
> On Mon, Jun 15, 2015 at 5:42 AM, Benjamin Poulain <[email protected]> > wrote: > >> Targeting XHR specifically seems very easy to counter to me. Couldn't >> one just use the Fetch API or Sockets to work around the rule? >> > > I don't think so. Note that with the new content blocking API you cannot > run code on request anymore. And even then you probably don't want to > repeat requests just to retrieve additional metadata. And even then the > response won't tell you in which context the request originally occurred. > Sorry, I just realized what you meant here. (I mistakenly thought you suggested to repeat requests to obtain additional metadata). But yeah, if a page uses the Fetch API, rules checking for XMLHttpRequest wouldn't match, however filters checking for "other" request types should match then. The distinction between XMLHttpRequest and Fetch API doesn't seem to be important. We might merge them into a common type in the future. However, the distinction between these, JavaScript initiated, requests and object (Flash) initiated requests is kinda important for us, as explained in my previous email. Sebastian
_______________________________________________ webkit-help mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-help
