You need to be logged in to post in the forums. If you do not have an account, please sign up first.
Cross Domain Error
Howdy. Wonder if anyone can help.Since a few versions ago, I'm having a problem, and it's driving me mad, even to the point of considering using Chrome or something. That's how bad it is.
Anyway, 'cos I live in China, I occasionally use some VPN software to access certain sites that are blocked by the ironically named, 'great firewall' of China.
So, I switch this VPN software on, browse away, and then switch it off. However, when I turn it off, just about every site I try to visit in Opera comes up with a 'Cross Domain Error'. It does offer me the chance to continue, but when I click on continue, or even Always continue, it simply pumps up the same error screen again. I have to exit Opera and restart to get it working again.
Can anyone tell me how to get rid of this error? Is there a security setting I can turn off, 'cos I'm going insane.
Many thanks in advance.
Originally posted by Chinren:
So, I switch this VPN software on, browse away, and then switch it off. However, when I turn it off, just about every site I try to visit in Opera comes up with a 'Cross Domain Error'.
That is probably because the VPN software has been DNS resolving the names of public sites to intranet IP addresses, rather than using the routing tables to direct all traffic through the VPN route which would be the proper way for the VPN software to achieve this.
For security reasons Opera does not allow a DNS name to be first resolved to one address category, e.g. public, then later resolved to a different one, e.g intranet, as this can be used in attacks against company networks.
The only way to force Opera to forget the address category without a shutdown is to use the "Sensitive Data" option in Delete Private Data (which will also destroy all SSL session and currently logged in HTTP session credentials, and other sensitive data)
Sincerely,
Yngve N. Pettersen
Yngve N. Pettersen
dlcarraw: It might still be possible that the DNS for those servers are badly configured, or the sites direct you to sites that crosses the address category boundary.
I work for software company and I am sorry, but this approach is making me crazy.
Right now, I have problem to access our company https:\\exchange..... web
It was working yesterday, day before, and days before (some other www pages not), now I can't access this exchange. It has nothing to do with DNS, because due to my work I am using lot different browsers and all except Opera works fine.
Can you explain me, why I am getting this error only sometimes and only with Opera? (only one rule - once it is not working while I am using some specific connection, it is not working at all... but maybe tomorrow everything will be ok again....as few times happened... )
Sorry, I really love Opera, saving of certificates, fast login etc... but THIS IS DRIVING ME CRAZY!
Don't blame DNS please again. I understand, it can be wrong settings by them, but anyway, I don't think all www developers of problematic sites are going to change all the settings due to incompatibility with Opera. More likely is that Opera have to work with that settings as all others do. Otherwise users will have to search for another browser, they don't want to use one browser for "opera compatible www" and second for "opera non compatible"
If I can help, just tell me, what You want me to send, log files, some test results...
Heyyyy.... I found something... I am connected on LAN and Wi-Fi is turned on... (but I never connected any Wi-Fi in this Area)
So, just to be sure, i turned off wi-fi and... voilá... it is working. Our company exchange without any problem.
eeee... what exactly this have to do with DNS????? I think it is more relate to some internal procedure.. but don't know exactly what...
So, my experience.... turn off connection that You don't need.... but....hmmm... VPN... nice challenge... You need two active connections...
So, just to be sure, i turned off wi-fi and... voilá... it is working. Our company exchange without any problem.
eeee... what exactly this have to do with DNS????? I think it is more relate to some internal procedure.. but don't know exactly what...
So, my experience.... turn off connection that You don't need.... but....hmmm... VPN... nice challenge... You need two active connections...
Originally posted by WolfNet:
what exactly this have to do with DNS?
Each connection has its own set of DNS servers configured. If they are able to resolve the same names, but to different IP addresses (because of which network they are on), then it could be a question of which server answers first. Generally, though, the same servername should never resolve to a different IP address.
Sincerely,
Yngve N. Pettersen
Yngve N. Pettersen