[webkit-help] content whitelisting by http referrer header/ 50k rule limit

[Charles]

Thanks for the response.

It's a user use case.  When a page doesn't work correctly, the user should
be able to whitelist the page/domain.
The problem is that usually what was blocked is hosted on a different
domain, so the other rules will still apply, and the users page still looks
"broken".

 Users don't and shouldn't have to understand that. And we shouldn't be
putting them through a page inspection process.

 But if we can do a referrer allowed, then a lot of whitelist rules will
compact down into a single rule, and ease of use goes up, and the user is
happy that their page at least works.

Also, I've been looking at the code, and playing with the json, is there a
way to do combine action selectors (multiple actions per trigger or
multiple selectors per action)? It doesn't appear so.

This is just an example, but a lot of the easylist converts to basically
the same thing over and over, just with the different selectors.
I don't think that can be as efficient. I could be wrong on that, but it's
also burning the 50k limit. And 11MB of text for the whole list.
I'm down to line 58,000 and the http(s) blanket is still going, at 8 lines
per rule, that's 7500 rules. After compiling probably isn't that big of a
deal, and internally would probably have to make it work just the same as
the larger json file works anyways.


Thanks again!

        {

                "trigger": {

                        "url-filter": "^https?://"

                },

                "action": {

                        "type": "css-display-none",

                        "selector": "#A9AdsOutOfStockWidgetTop"

                }

        },

        {

                "trigger": {

                        "url-filter": "^https?://"

                },

                "action": {

                        "type": "css-display-none",

                        "selector": "#A9AdsServicesWidgetTop"

                }
        },


On Tue, Sep 22, 2015 at 5:06 PM, Alex Christensen <achristensen at apple.com>
wrote:

>
> > On Sep 22, 2015, at 2:47 PM, Charles Butkus <airdamien at gmail.com> wrote:
> >
> > Is it currently possible to write rules against http referrer?
> It is not currently possible to do anything with the HTTP headers.
> >
> > I’m looking through the code and it doesn’t seem to be.
> >
> > If a user wants to whitelist blocked content on a page hosted on a
> different domain, what’s the expected way of enabling this? In my head, I’d
> go after the referrer and whitelist based on that. if-domain and/or
> url-filter.
> What exactly is your use case?  Do you want to whitelist everything that
> you see after clicking on a link from a certain domain, no matter where
> that link goes?  That is currently impossible with content blockers.
> >
> > Also, what’s the deal with the 50k rule limit? I’m assuming it’s for
> performance, but the current easylist is  46,879 entries by itself after
> conversion.
> You assume correctly.  It can take a lot of time and memory to compile 50k
> rules.
> > I need to look at the data and see what I can trim down into rules with
> more coverage.
> >
> > Thanks!
> > _______________________________________________
> > webkit-help mailing list
> > webkit-help at lists.webkit.org
> > https://lists.webkit.org/mailman/listinfo/webkit-help
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-help/attachments/20150922/554cfe60/attachment.html>