Re: Transitive third party exceptions

Ideally, yes.

On Wed, May 9, 2012 at 9:15 AM, Ionel Naftanaila <training@iabeurope.eu>wrote:

>  Ian,
>
>  I believe the text below should accommodate the ad chain issue, at least
> from a technical perspective. Just one question:
>
>  Building on your text below, if “Site A” is an Ad Server, in a large
> number of cases the redirect will be simply done via JavaScript - i.e.
> “Site A” replies with a JavaScript code calling “Site B”.  Will the below
> be implementable from a browser perspective, considering that we might be
> seeing a large number of such redirects if we’re in the situation described
> above?
>
>       Thanks,
>
> Ionel
>
>  On 9 May 2012, at 18:37, Ian Fette (イアンフェッティ) wrote:
>
> This is meant to satisfy ACTION-194 and is a proposal for transitive third
> party exceptions. I'm not sure if it's necessary if we restrict things to
> "first-party/*" but if you want to list out "first-party/third-party"
> explicit/explicit exceptions, I believe it would be necessary for things
> like advertising networks to function.
>
>  "If a third party has been granted an exception on a page, then any
> resources fetched by that third party, including items such as images
> included by that third party, content dynamically fetched by that third
> party, or another third party that is redirected to (such as via an HTTP
> 302 status code) are considered to be covered by that exception. This
> applies transitively, meaning that if in a given context "Site A" is a
> third party and has an exception, if it redirects to "Site B" then "Site B"
> is covered by that exception, as would "Site C" if "Site B" either included
> content from or redirected to "Site C".
>
>  -Ian
>
>
>