Remove Google Analytics cookie
up vote
0
down vote
favorite
We had an wrong script inserted by Google Tag Manager on our page, that caused 403 error. The script was removed and after wiping out the cookies (or just _gs cookie) our page works fine.
The problem is that the users, who entered the page when we had the wrong script still have the _gs cookie, and they still get 403 error.
How can we make their browsers remove that cookie, while our index page is not even reached?
The setup is a Sitecore CMS set up on IIS 10.
iis cookies
google-analytics http-status-code-403 asked Nov 19 at 16:28
Piotr Zaborowski
63
add a comment |
up vote
0
down vote
favorite
We had an wrong script inserted by Google Tag Manager on our page, that caused 403 error. The script was removed and after wiping out the cookies (or just _gs cookie) our page works fine.
The problem is that the users, who entered the page when we had the wrong script still have the _gs cookie, and they still get 403 error.
How can we make their browsers remove that cookie, while our index page is not even reached?
The setup is a Sitecore CMS set up on IIS 10.
iis cookies
google-analytics http-status-code-403 asked Nov 19 at 16:28
Piotr Zaborowski
63
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We had an wrong script inserted by Google Tag Manager on our page, that caused 403 error. The script was removed and after wiping out the cookies (or just _gs cookie) our page works fine.
The problem is that the users, who entered the page when we had the wrong script still have the _gs cookie, and they still get 403 error.
How can we make their browsers remove that cookie, while our index page is not even reached?
The setup is a Sitecore CMS set up on IIS 10.
iis cookies
google-analytics http-status-code-403 asked Nov 19 at 16:28
Piotr Zaborowski
63
We had an wrong script inserted by Google Tag Manager on our page, that caused 403 error. The script was removed and after wiping out the cookies (or just _gs cookie) our page works fine.
The problem is that the users, who entered the page when we had the wrong script still have the _gs cookie, and they still get 403 error.
How can we make their browsers remove that cookie, while our index page is not even reached?
The setup is a Sitecore CMS set up on IIS 10.
iis cookies
google-analytics http-status-code-403 iis cookies
google-analytics http-status-code-403 asked Nov 19 at 16:28
Piotr Zaborowski
63
asked Nov 19 at 16:28
Piotr Zaborowski
63
asked Nov 19 at 16:28
Piotr Zaborowski
63
asked Nov 19 at 16:28
Piotr Zaborowski
63
asked Nov 19 at 16:28
Piotr Zaborowski
63
63
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
You can try "expiring" the cookie. All that would need to be done is add that cookie back but with the expiration date set to a date/time in the past. That way the cookie would be treated as expired and would pick up the new value if it exists.
answered Nov 19 at 16:46
IgorKol
856
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
add a comment |
up vote
0
down vote
accepted
Identifying the root cause helped to solve the problem.
Our application is set up on Azure VM, but the connection is through Application Gateway, which has a firewall. Apparently, the firewall considered the content of the mentioned _gs cookie suspcious, and it was the Application Gateway, that returned 403, and not the IIS itself.
Adding the _gs cookie to the whitelist solved the problem.
answered Nov 20 at 7:05
Piotr Zaborowski
63
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You can try "expiring" the cookie. All that would need to be done is add that cookie back but with the expiration date set to a date/time in the past. That way the cookie would be treated as expired and would pick up the new value if it exists.
answered Nov 19 at 16:46
IgorKol
856
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
add a comment |
up vote
0
down vote
You can try "expiring" the cookie. All that would need to be done is add that cookie back but with the expiration date set to a date/time in the past. That way the cookie would be treated as expired and would pick up the new value if it exists.
answered Nov 19 at 16:46
IgorKol
856
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
add a comment |
up vote
0
down vote
up vote
0
down vote
You can try "expiring" the cookie. All that would need to be done is add that cookie back but with the expiration date set to a date/time in the past. That way the cookie would be treated as expired and would pick up the new value if it exists.
answered Nov 19 at 16:46
IgorKol
856
You can try "expiring" the cookie. All that would need to be done is add that cookie back but with the expiration date set to a date/time in the past. That way the cookie would be treated as expired and would pick up the new value if it exists.
answered Nov 19 at 16:46
IgorKol
856
answered Nov 19 at 16:46
IgorKol
856
answered Nov 19 at 16:46
IgorKol
856
answered Nov 19 at 16:46
IgorKol
856
856
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
add a comment |
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
That was my idea, but the problem was that I couldn't get my code executed, because the request didn't reach my page.
– Piotr Zaborowski
Nov 20 at 7:01
add a comment |
up vote
0
down vote
accepted
Identifying the root cause helped to solve the problem.
Our application is set up on Azure VM, but the connection is through Application Gateway, which has a firewall. Apparently, the firewall considered the content of the mentioned _gs cookie suspcious, and it was the Application Gateway, that returned 403, and not the IIS itself.
Adding the _gs cookie to the whitelist solved the problem.
answered Nov 20 at 7:05
Piotr Zaborowski
63
add a comment |
up vote
0
down vote
accepted
Identifying the root cause helped to solve the problem.
Our application is set up on Azure VM, but the connection is through Application Gateway, which has a firewall. Apparently, the firewall considered the content of the mentioned _gs cookie suspcious, and it was the Application Gateway, that returned 403, and not the IIS itself.
Adding the _gs cookie to the whitelist solved the problem.
answered Nov 20 at 7:05
Piotr Zaborowski
63
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Identifying the root cause helped to solve the problem.
Our application is set up on Azure VM, but the connection is through Application Gateway, which has a firewall. Apparently, the firewall considered the content of the mentioned _gs cookie suspcious, and it was the Application Gateway, that returned 403, and not the IIS itself.
Adding the _gs cookie to the whitelist solved the problem.
answered Nov 20 at 7:05
Piotr Zaborowski
63
Identifying the root cause helped to solve the problem.
Our application is set up on Azure VM, but the connection is through Application Gateway, which has a firewall. Apparently, the firewall considered the content of the mentioned _gs cookie suspcious, and it was the Application Gateway, that returned 403, and not the IIS itself.
Adding the _gs cookie to the whitelist solved the problem.
answered Nov 20 at 7:05
Piotr Zaborowski
63
answered Nov 20 at 7:05
Piotr Zaborowski
63
answered Nov 20 at 7:05
Piotr Zaborowski
63
answered Nov 20 at 7:05
Piotr Zaborowski
63
63
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378924%2fremove-google-analytics-cookie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
