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
![Create A Cookie Rewrite Web Service Using The Google Cloud Platform](https://cdn-ak-scissors.b.st-hatena.com/image/square/6b0a788f01d852b359bb4d9c705ebfa489826c0f/height=288;version=1;width=512/https%3A%2F%2Fwww.simoahava.com%2Fimages%2F2019%2F06%2Fsafari-cookies.jpg)