Quote:
Originally Posted by Paul&John
Thanks for the reply, but this needs to be edited in the Statcounter code itself which gets provided by them, no?
I mean the cookie set by statcounter is this for example:
Code:
__cfduid=dd67a3df3519a5b4e1585056313; expires=Thu, 23-Apr-20 13:25:13 GMT; path=/; domain=.statcounter.com; HttpOnly; SameSite=Lax
And this is the example code added to the footer
Code:
<script type="text/javascript">
var sc_project=2197334;
var sc_invisible=0;
var sc_security="d176e8f6";
var scJsHost = "https://";
document.write("<sc"+"ript type='text/javascript' src='" +
scJsHost+
"statcounter.com/counter/counter.js'></"+"script>");
</script>
<noscript><div class="statcounter"><a title="Web Analytics"
href="https://statcounter.com/" target="_blank"><img
class="statcounter"
src="https://c.statcounter.com/2197334/0/d176e8f6/0/"
alt="Web Analytics"></a></div></noscript>
so they need to add that SameSite=none; Secure part into the .js ( statcounter.com/counter/counter.js ) , right? I cant overwrite it on my end from Lax to None? |
Yes.
You can't do anything about another site's cookie.
They have to fix it on their end.
Now quit stalling on the toilet paper, I will no longer accept $500 Billion.
