Cookiebot removes all javascript even though it is marked as 'ignore'
We are experiencing an issue with Cookiebot, where it removes all JavaScript, despite the JavaScript being explicitly marked as data-cookieconsent="ignore". We use it in auto blocking mode and the behavior if the bug occurs is such:
- Cookiebot removes all content from page and just puts the modal for consent
- In Network monitor I see one fetch request to the same URL done of the page, which originates from Cookiebot. On our configuration this is responded with a 404 from server (since we have some code that prevents giving HTML to random fetch requests like that)
- After consent of only necessary the page is completely blank and unusable (Serious Bug)
- After consent of all cookies, the page is completely blank and unusable until a page reload at which point it is usable.
This behavior is consistently reproducible on Microsoft Edge on MacOS at the very least. On Chrome for example, this behavior does not appear and I also do not see CookieBot doing the above mentioned fetch request to the page.
-
Hello,
same issue on my website. I can reprocude it on Microsoft Edge on Windows 10. Have anyone an idea?
Thanks.
0 -
As far as I see it is related to the 404 which is caused by the request from Cookiebot requesting the page without any 'Accept' header, which I would consider odd. Also, I am not sure why Cookiebot even requests the page twice. I think this can have also some other non-ideal side effects for other people e.g. tracking related. I now moved our code to allow returning the page for empty Accept headers, but I still consider this buggy on Cookiebot side.
1 -
I am also experiencing these issues on multiple websites. I have been able to reproduce this behaviour on both Mac OSX and Windows Edge browsers. All other browsers seem to work properly with no issues.
After further testing I can confirm exactly the same behaviour as Patrick described in the opening message.
1 -
Has anyone an idea for a fix?
0 -
Hi i have same issue. I don't know what is the reason behind it.
0 -
I'm still facing this issue, let me know if someone has find its solution at my website.
0
Please sign in to leave a comment.
Comments
6 comments