By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,795 Members | 1,761 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,795 IT Pros & Developers. It's quick & easy.

3+ concurrent connections and parent.function()

P: 6
I have a need to have three plus frames with concurrent connections to a web server, and all of them able to communicate with the parent page.

To overcome the 2 concurrent connections limit I used CNAMEs for each of the frames, but now parent.function() doesnt work because the browser considers the CNAMEs to be different sites and gives a permissions error.

Is this a Catch22? Is there a cross public browser way around it?

TIA

Zom.
Sep 25 '07 #1
Share this Question
Share on Google+
3 Replies


dmjpro
100+
P: 2,476
I have a need to have three plus frames with concurrent connections to a web server, and all of them able to communicate with the parent page.

To overcome the 2 concurrent connections limit I used CNAMEs for each of the frames, but now parent.function() doesnt work because the browser considers the CNAMEs to be different sites and gives a permissions error.

Is this a Catch22? Is there a cross public browser way around it?

TIA

Zom.
Look if a Browser have multiple sites in one window using multiple frames.
Then communicate with each frame can't be done for security reason.
I mean JavaScript does not support Cross-Site scripting.

Post here your code.
And what you trying to do let me know us.

Kind regards,
Dmjpro.
Sep 25 '07 #2

P: 6
zom
Thanks for the reply dmjpro.

There is about 13000 lines of PHP script with this issue as a very small part of it so forgive me if I dont post code.

Have a look at http://irmp.at/demo to see a simple top level of the implementation.

I know why the problem is happening. I am asking if there is a (clever or otherwise) way around it.

My application is not actually cross site. It is only one site using a number of CNAMEs that all point to the same IP address. The CNAMEs make javascript think it is cross site when it is not.

Is there perhaps some way of authoritatively telling JS that the sub-domains are really not different sites because they all have the same base domain?

From what you say, probably not.

Cheers,

Zom.
Sep 26 '07 #3

P: 6
zom
Never mind dmjpro.

I found a way around my problem by using CNAMEs on the second and later instances after the parent communications was no longer needed.

Cheers,

Zom.
Sep 26 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.