Origin Policy violation on google.by pages
up vote
1
down vote
favorite
Starting from today I'm constantly getting this error when trying to search something at google.by:
Well, well, well. What do we have here? An Origin Policy violation.
And what do we not have? A page!
You're trying to go to:
https://www.google.by/search?q=thymeleaf+is+0+or+zero&sourceid=chrome&ie=UTF-8
The policy applies to: https://www.google.by
I tried other domains (google.com, google.ru, google.de) and they are working fine. The issue is reproducible in incognito mode (with plugins disabled). In Chrome only (Firefox and Edge have no such problem) and it started recently, so it may be related to the recent Chrome update. Now I use Chrome Version 71 (Beta).
- What does it mean?
- I didn't change something in my connection settings. Who is in charge? Google? ISP?
google-search security-policy
asked 7 hours ago
naXa
1106
add a comment |
up vote
1
down vote
favorite
Starting from today I'm constantly getting this error when trying to search something at google.by:
Well, well, well. What do we have here? An Origin Policy violation.
And what do we not have? A page!
You're trying to go to:
https://www.google.by/search?q=thymeleaf+is+0+or+zero&sourceid=chrome&ie=UTF-8
The policy applies to: https://www.google.by
I tried other domains (google.com, google.ru, google.de) and they are working fine. The issue is reproducible in incognito mode (with plugins disabled). In Chrome only (Firefox and Edge have no such problem) and it started recently, so it may be related to the recent Chrome update. Now I use Chrome Version 71 (Beta).
- What does it mean?
- I didn't change something in my connection settings. Who is in charge? Google? ISP?
google-search security-policy
asked 7 hours ago
naXa
1106
Does this happen if you do it immediately at the start a new Chrome session? Just close all windows of Chrome, start it again and issue the query.
– harrymc
7 hours ago
@harrymc No, the problem is gone after restart. I still don't know the cause of it. Chrome update and Tampermonkey plugin update are the main suspects.
– naXa
5 hours ago
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Starting from today I'm constantly getting this error when trying to search something at google.by:
Well, well, well. What do we have here? An Origin Policy violation.
And what do we not have? A page!
You're trying to go to:
https://www.google.by/search?q=thymeleaf+is+0+or+zero&sourceid=chrome&ie=UTF-8
The policy applies to: https://www.google.by
I tried other domains (google.com, google.ru, google.de) and they are working fine. The issue is reproducible in incognito mode (with plugins disabled). In Chrome only (Firefox and Edge have no such problem) and it started recently, so it may be related to the recent Chrome update. Now I use Chrome Version 71 (Beta).
- What does it mean?
- I didn't change something in my connection settings. Who is in charge? Google? ISP?
google-search security-policy
asked 7 hours ago
naXa
1106
Starting from today I'm constantly getting this error when trying to search something at google.by:
Well, well, well. What do we have here? An Origin Policy violation.
And what do we not have? A page!
You're trying to go to:
https://www.google.by/search?q=thymeleaf+is+0+or+zero&sourceid=chrome&ie=UTF-8
The policy applies to: https://www.google.by
I tried other domains (google.com, google.ru, google.de) and they are working fine. The issue is reproducible in incognito mode (with plugins disabled). In Chrome only (Firefox and Edge have no such problem) and it started recently, so it may be related to the recent Chrome update. Now I use Chrome Version 71 (Beta).
- What does it mean?
- I didn't change something in my connection settings. Who is in charge? Google? ISP?
google-search security-policy
google-search security-policy
asked 7 hours ago
naXa
1106
asked 7 hours ago
naXa
1106
edited 7 hours ago
asked 7 hours ago
naXa
1106
asked 7 hours ago
naXa
1106
asked 7 hours ago
naXa
1106
1106
Does this happen if you do it immediately at the start a new Chrome session? Just close all windows of Chrome, start it again and issue the query.
– harrymc
7 hours ago
@harrymc No, the problem is gone after restart. I still don't know the cause of it. Chrome update and Tampermonkey plugin update are the main suspects.
– naXa
5 hours ago
add a comment |
Does this happen if you do it immediately at the start a new Chrome session? Just close all windows of Chrome, start it again and issue the query.
– harrymc
7 hours ago
@harrymc No, the problem is gone after restart. I still don't know the cause of it. Chrome update and Tampermonkey plugin update are the main suspects.
– naXa
5 hours ago
Does this happen if you do it immediately at the start a new Chrome session? Just close all windows of Chrome, start it again and issue the query.
– harrymc
7 hours ago
Does this happen if you do it immediately at the start a new Chrome session? Just close all windows of Chrome, start it again and issue the query.
– harrymc
7 hours ago
@harrymc No, the problem is gone after restart. I still don't know the cause of it. Chrome update and Tampermonkey plugin update are the main suspects.
– naXa
5 hours ago
@harrymc No, the problem is gone after restart. I still don't know the cause of it. Chrome update and Tampermonkey plugin update are the main suspects.
– naXa
5 hours ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The reason for such a problem that the answer returned by google.by
tried to access data which was stored by a previous website request.
Wikipedia Same-origin policy
explains well the problem:
The following example illustrates a potential security risk that could arise without the same-origin policy. Assume that a user is visiting a banking website and doesn't log out. Then, the user goes to another site that has some malicious JavaScript code running in the background that requests data from the banking site. Because the user is still logged in on the banking site, the malicious code could do anything the user could do on the banking site. For example, it could get a list of the user's last transactions, create a new transaction, etc. This is because the browser can send and receive session cookies to the banking site based on the domain of the banking site.
I have no real idea why issuing a query on google.by would cause a
reference that would trigger a same-origin policy block, but it is clear
that this has prevented an inappropriate access to your data.
Google is one of the most-used avenues for malware, so it's possible that its
ads system brought you a shady reference.
If this happens again, do the same thing: Restart Chrome.
The chances are that the same ad won't be served again.
answered 1 hour ago
harrymc
247k10255542
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
The reason for such a problem that the answer returned by google.by
tried to access data which was stored by a previous website request.
Wikipedia Same-origin policy
explains well the problem:
The following example illustrates a potential security risk that could arise without the same-origin policy. Assume that a user is visiting a banking website and doesn't log out. Then, the user goes to another site that has some malicious JavaScript code running in the background that requests data from the banking site. Because the user is still logged in on the banking site, the malicious code could do anything the user could do on the banking site. For example, it could get a list of the user's last transactions, create a new transaction, etc. This is because the browser can send and receive session cookies to the banking site based on the domain of the banking site.
I have no real idea why issuing a query on google.by would cause a
reference that would trigger a same-origin policy block, but it is clear
that this has prevented an inappropriate access to your data.
Google is one of the most-used avenues for malware, so it's possible that its
ads system brought you a shady reference.
If this happens again, do the same thing: Restart Chrome.
The chances are that the same ad won't be served again.
answered 1 hour ago
harrymc
247k10255542
add a comment |
up vote
0
down vote
accepted
The reason for such a problem that the answer returned by google.by
tried to access data which was stored by a previous website request.
Wikipedia Same-origin policy
explains well the problem:
The following example illustrates a potential security risk that could arise without the same-origin policy. Assume that a user is visiting a banking website and doesn't log out. Then, the user goes to another site that has some malicious JavaScript code running in the background that requests data from the banking site. Because the user is still logged in on the banking site, the malicious code could do anything the user could do on the banking site. For example, it could get a list of the user's last transactions, create a new transaction, etc. This is because the browser can send and receive session cookies to the banking site based on the domain of the banking site.
I have no real idea why issuing a query on google.by would cause a
reference that would trigger a same-origin policy block, but it is clear
that this has prevented an inappropriate access to your data.
Google is one of the most-used avenues for malware, so it's possible that its
ads system brought you a shady reference.
If this happens again, do the same thing: Restart Chrome.
The chances are that the same ad won't be served again.
answered 1 hour ago
harrymc
247k10255542
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The reason for such a problem that the answer returned by google.by
tried to access data which was stored by a previous website request.
Wikipedia Same-origin policy
explains well the problem:
The following example illustrates a potential security risk that could arise without the same-origin policy. Assume that a user is visiting a banking website and doesn't log out. Then, the user goes to another site that has some malicious JavaScript code running in the background that requests data from the banking site. Because the user is still logged in on the banking site, the malicious code could do anything the user could do on the banking site. For example, it could get a list of the user's last transactions, create a new transaction, etc. This is because the browser can send and receive session cookies to the banking site based on the domain of the banking site.
I have no real idea why issuing a query on google.by would cause a
reference that would trigger a same-origin policy block, but it is clear
that this has prevented an inappropriate access to your data.
Google is one of the most-used avenues for malware, so it's possible that its
ads system brought you a shady reference.
If this happens again, do the same thing: Restart Chrome.
The chances are that the same ad won't be served again.
answered 1 hour ago
harrymc
247k10255542
The reason for such a problem that the answer returned by google.by
tried to access data which was stored by a previous website request.
Wikipedia Same-origin policy
explains well the problem:
The following example illustrates a potential security risk that could arise without the same-origin policy. Assume that a user is visiting a banking website and doesn't log out. Then, the user goes to another site that has some malicious JavaScript code running in the background that requests data from the banking site. Because the user is still logged in on the banking site, the malicious code could do anything the user could do on the banking site. For example, it could get a list of the user's last transactions, create a new transaction, etc. This is because the browser can send and receive session cookies to the banking site based on the domain of the banking site.
I have no real idea why issuing a query on google.by would cause a
reference that would trigger a same-origin policy block, but it is clear
that this has prevented an inappropriate access to your data.
Google is one of the most-used avenues for malware, so it's possible that its
ads system brought you a shady reference.
If this happens again, do the same thing: Restart Chrome.
The chances are that the same ad won't be served again.
answered 1 hour ago
harrymc
247k10255542
answered 1 hour ago
harrymc
247k10255542
answered 1 hour ago
harrymc
247k10255542
answered 1 hour ago
harrymc
247k10255542
247k10255542
add a comment |
add a comment |
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%2fsuperuser.com%2fquestions%2f1375982%2forigin-policy-violation-on-google-by-pages%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
Does this happen if you do it immediately at the start a new Chrome session? Just close all windows of Chrome, start it again and issue the query.
– harrymc
7 hours ago
@harrymc No, the problem is gone after restart. I still don't know the cause of it. Chrome update and Tampermonkey plugin update are the main suspects.
– naXa
5 hours ago