Method 3 does not work… the main page will not be able to access the IFRAME contents if it is not from the same domain.

Yeah I found out that that didn’t work a while ago. Method 1 is probably the best way to go.

Method 1 works fine, but … what if the page that I am trying to get depends on sessions or cookies (displays different content depending on the client – for example the total amount in a shopping cart). Can this be sorted out somehow?

John you can pass that information through the script in the query string or you can send that information through using a POST request. You pass the information to the PHP script and the PHP script passes it along.

I wonder if Method 2 would even work. Sure, your iframe can contact the service, but the results can not be written into the main frame using javascript because I believe the browser would treat the frame and iframe as two different domains (even if just the port is different). Anyone even tried this?

Hi Nathan, I’m trying to implement method 2 but I’m having difficulties in getting it working. I’m pretty new to the whole XHR cross-domain thing, am I right in thinking that if I want to make XHR requests from localhost:8080 to say localhost:8181 then method 2 is the right way to tackle this? I was also wondering if you had any sample code available? or any more details on this? Thanks

This was a long time ago. From what I remember I believe I got it Method 2 working, but I am not sure about it working on both browsers.

Actually what I’ve found, is that instead of creating a NT service and trying to use AJAX to connect to it on another port, it is better to just create an IIS ISAPI extension. IIS would host the ISAPI extension on the same domain. Then you could use AJAX to contact the ISAPI extension which could do whatever you wanted. Even gather information from database or get information from another site.

For more information on what an ISAPI extension is or how it works with IIS see,

http://www.codeproject.com/KB/ISAPI/isapi_extensions.aspx

Method 4
I use a ProxyPass in the apache config to get around this. It looks like this.
ProxyPass /XML http://otherserver:8080/XML

In this case you have your ajax hit /XML? and apache will forward the request to http://otherserver:8080/XML?

Method 3 is not working and will not work at all

I found an other solution for cross domain things.

They says it’s JSON, but I think it isn’t:
http://www.javaworld.com/javaworld/jw-11-2006/jw-1115-json.html?page=2

Based upon this, I made a simple test:
http://linked.drag2web.com/crossdomain/

Method 3 does not work straight away as the iframe can not communicate with the parent if it is from an outside domain.

I have written an article on how to overcome this, take a look here:
http://varjabedian.net/archive/2008/08/12/faster-asp.net-ajax-websevices-through-multiple-sub-domain-calls.aspx

Yes I have just checked it and method 3 is not working for me as well.

It looks like the one way to handle this has nothing to do with XMLHttpRequest. It’s called JSONP, and it requires you adhere to some conventions on the output your server returns. The trick is not to use iframes of XMLHttpRequests but instead to use JavaScript to dynamically create a request. You can pass data to the server via query strings parameters (a la “GET”) and you have the server return JSON-based data. Dojo and jQuery both implement this solution now.

Hi,

Method1: Can we have a sample code? Preferable Classic ASP+javascript

thx
Jeff

Method 2 & 3 can work if both of them read and write to window.name

This is another resource which will be of help – http://piecesofrakesh.blogspot.com/2007/11/how-to-build-readwrite-javascript-api.html

Here is a solution http://www.ajax-cross-domain.com/ . Other posibility to solve cross-domain restriction is to use Flex. I didn’t try it, but it could be possibly ok.

thanks for this…
Regards
Sharad