![Cross-browser tracking vulnerability in Tor, Safari, Chrome and Firefox - Fingerprint](https://cdn-ak-scissors.b.st-hatena.com/image/square/f18538d9026fccf825e3c85ea2faf9735205fc0f/height=288;version=1;width=512/https%3A%2F%2Ffingerprint.com%2Fstatic%2F5511724fc0c55aa9c6694c3865877f98%2Fcross-browsers-article-cover.png)
However, Safari does not (currently) cap cookies set with the Set-Cookie HTTP header. Why? Because creating a setup that makes use of the Set-Cookie header requires developer resources and is always a deliberate decision how to handle first-party persistence. ITP’s main beef is against third-party JavaScript libraries executing code that repurposes first-party storage for something other than firs
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く