We are starting an important project with CourseLab, producing eLearning courses.

We have an internal AICC compliant Platform and we are experiencing some problems.

The most important is the following:
In our organization the courses are delivered from a web server which is different from the one that hosts the Learning Management System. Nevertheless both server are on the same primary domain:

LMS server responds to the address: learning.ourdomain.com

The courses are delivered from: courses.ourdomain.com

In this configuration the course javascript in CourseLab that is supposed to contact the CMI component specified by the AICC_URL parameter is raising an error [object Error]. What happens is that the course page is started and after a while the error pops up two times, it pops up again when the course window is closed.

There might be some security problem that prevents the javascript form contacting the AICC_URL correctly? Are you using frames or IFrames in the course page that cannot be accessed because of cross-domain security reasons?

We have tried copying the course content on LMS server and the problem disappears. The point is that it is impossible for us to have both the contents and the LMS application on the same server, due to load balancing and storage issues.

How is it possible to solve this problem?

Thanks in advance for an answer

Sandro

Hi Sandro
Welcome to the world of browser security, the browser is interpreting the *****/name1.name1.com and *****/name2.name1.com as different domains. This is a deliberate action to prevent script in a page redirecting to another page which usually isn't considered a friendly act. This has been the case for quite a while and any half competent IT tech should have realised that this would happen. This is well documented in pretty much all browser support documentation.

The easiest way to get around this is to invest in a server that is adequate for the task which will make life much easier. Which isn't the answer you are looking for but is the best option.

Failing that you could try setting the domain property of the documents (in the DHTML document model)to use the domain name determined by the server instead of the domain name determined by the client browser.
All the pages on your two hosts must have the domain property explicitly set to the same value to communicate successfully with each other. Your problem will go away or just be hidden by spoofing the browser itself.
However (isn't their always one)I wouldn't advise this if you are operating these servers on the INTERNET as it is causes quite a high security risk. A fairly simple DNS exploit will leave your server wide open!! [:mad:]
If they are INTRANET based then it is an option assuming your support team have the skills/experience to handle the task.

Hi Nickj and many thanks for the detailed answer. I'll investigate and trying setting the domain property of our documents as you suggest...

Thanks again

Sandro