3 ms·
Assuming I'm understanding your question correctly, yes, you would have something like: <iframe src="https://saasapp.com/report?url= https://mydomain.com
by a1369209993 7y ago
Assuming I'm understanding your question correctly, yes, you would have something like:
<iframe src="https://saasapp.com/report?url=
https://mydomain.com/data/1234.json%3F
v%3D42%26auth%3D__79_Pv6-fj39vX08_Lx8A++"/>
(spaces added for readability)
- tetraca 7y agoCool, if third party tracking cookies are "defeated", this will be the next step in the arms race.
- a1369209993 7y agoThis site includes content from saasapp.com: [Whitelist INC saasapp.com From mydomain.com] [Blacklist saasapp.com] [Allow once] [Ignore]
- tetraca 7y agoI'd be happy with that.
- baroffoos 7y agoThat could work well because if the message shows the domain that looks like the content they want to see they will allow it but if its a random tracker domain they will block it.
- a1369209993 7y agoIt's also important to not include [Whitelist INC i.imgur.com], only [Whitelist INC i.imgur.com FROM example.com], because trackers will adapt to exploit the first one as soon as it's common enough to be noteworthy.
- yholio 7y agoIf browsers break 3rd party cookies and they are not fingerprintable, the arms race stops: there is no way to track a client across multiple sites, other than weak correlations with IP, interests, etc.