Have looked within AW forum for a similiar issue with no success (except Mozilla, which I'm not sure is the same issue).
In particular, I have an asp page that returns XML, so I have:
table.setURL("a asp file within my domain");
And then a request:
It is within the table.request call that the "permission denied" occurs.
Any ideas? I have read elsewhere that it may be a caching or registry issue, but wanted to get advice from the masters!
I'll keep trying - have come a long way just to punt!
Any suggestions would be appreciated.
Or what ever flavor of script you are calling. BUt permissions usually mean something is happening. What browser are you using? If you use Firefox the JS console usually gives better errors than IE poop errors.
I discovered - although I thought I had already tried - that setting
Internet Options -> Security/Internet/Custom Level -> Miscellaneous ->
Access data source across domains
to ENABLED - IT WORKS!!.
I will try Tony's suggestion tomorrow. Hopefully we can avoid having our clients mucking around in their Internet Options.
Does this mean that, in fact, I am accessing data across domains?
Thanks for the help (and for future help).
The web app is opened with URL #1, XML is retrieved with URL #2 - specified in the AW setURL() method. This situation caused the "Cross Domain" issue. Changing URL #2 to
cured what IE thought was a "Cross Domain" issue. Still not sure why IE thought this, but I'm happy to leave it as a mystery and move on!
It seems that by providing the www. vs. not providing it somehow causes the error.
Oh, and please don't fall into the media trap, and inexperienced programmer trap of calling it "AJAX".
It's called RemoteScripting.....If they wanted to come up with a different name for it, then it should do something different. RemoteScripting has been around and in use since at least 1996.
This topic is archived.
Back to support forum
Version 2Looking for AW 2.6 ?
The old site is here.