you probably know this, but cookies are sent with every damn request the client makes. So it's a tax, It may be a small % of total traffic, but most of the time, it's useless.
It's easy to work around this in a backwards compatible way, though, in a way that's applicable to more than just cookies - in requests after the first, only re-send headers that have changed.
Or just live with the hit while sites migrate to the new mechanism; I'm fine with it being considered a legacy thing.
Or just live with the hit while sites migrate to the new mechanism; I'm fine with it being considered a legacy thing.