http vs https and dev console errors
Hi
I have a few issues issues. I wonder if you can please help?
I have just set up a paid account.
I have configured 2 domains on the Domains tab of the Cookiebot settings panel. Each domain has an alias as I am working locally, hooking up cookie logic and testing everything out.
Each alias is created using the "ngrok" tool (because "http://localhost:[PORT NUMBER]" does not work as a Domain alias)
Q1a: Why would I see cookies returned for one domain and not the other?
Q1b: Is this anything to do with one domain being served over https and the other being served over http?
Q2: I have some errors and warnings in the Google Chrome Dev Tools console panel. Can you advise?
ERROR 1:
Uncaught TypeError: e.data.replace is not a function
at CookieControl.Cookie.handleMessage (uc.js:1)
at uc.js:1
What is the most likely cause of this error?
WARNING 1:
WARNING! Internal test version. Cookie Consent not logged.
Uncaught TypeError: e.data.replace is not a function
at CookieControl.Cookie.handleMessage (uc.js:1)
at uc.js:1
Where it says "Cookie Consent is not logged" - can you clarify the situation here?
I mean, the cookie panel is present, everything is checked, the OK button has been clicked and in my mind, at that stage cookie consent is logged. Is that not the case?
If this is a restriction of using domain aliases for internal test reasons then how can I test my code/logic internally prior to it going live?
Any help and advice you can offer is much appreciated.
Thanks
James
-
Hey James,
Based on your other post, is everything okay at this point?
Have the issues been resolved?
Kind Regards,
Martin0 -
Hello Martin,
I also using domain aliases for internal test reason and saw the WARNING in the Google Chrome Dev Tools console panel.
WARNING! Internal test version. Cookie Consent not logged.
Can you conform that this is a normal behaviour when you use domain aliases for internal test domains ?
0
Please sign in to leave a comment.
Comments
2 comments