You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here, the domain of cookie xlly_s is .aliexpress.com, as displayed by consentcrawl as well . However, the initiator is external domain https://fourier.taobao.com.
Would it be possible to add the cookie initiators, so external loaded cookies can be identified?
The text was updated successfully, but these errors were encountered:
This is a really good question @Tedixx. It is definitely possible to implement, however it is not easy. I don't think there is any direct access to the request initiator chain that you are able to see e.g. in the Chrome dev tools. That means you'd have to intercept all requests (which we already do), but also follow redirects, keep track of child/parent relations, extract the cookie headers for each of these requests and write the logic to match and keep track of the initiator (excluding of course the domain you are currently on). Of course as a site owner you are ultimately responsible for all cookies and 3rd party requests regardless of where they come from, but I can understand how someone would want to catch any rogue cookies on their site coming from third party implementations.
The initiator of cookies is not displayed. This causes that users are unable to identify if a cookie is initiated locally or externally.
As sample: https://cookie-scanner.com/summary/www.aliexpress.com/?ucrid=CRICC05587bd0113af63f0cb9c32a568807ab
Here, the domain of cookie xlly_s is .aliexpress.com, as displayed by consentcrawl as well . However, the initiator is external domain https://fourier.taobao.com.
Would it be possible to add the cookie initiators, so external loaded cookies can be identified?
The text was updated successfully, but these errors were encountered: