Does anyone have orbited working in IE 8 using a different subdomain and port for the orbited host?

[Bjorn Tipling]

I cannot get this to work. I've tried all kinds of things such as
changing the security settings to lowest possible and adding the site
to trusted sites with lowest settings and it doesn't work.
The HTMLFileFrame.js cannot access parent.Orbited, permissions denied
even if the document.domain of the parent and the HTMLFileFrame.js
completely match.

So does anyone have orbited working with IE using different
subdomains? On my local setup using hosts I've set up test.com for the
main website, the parent and for the orbited host I have dev.test.com
for example, and it doesn't work unless they're both the same or I'm
using ipaddresses.

If you have it working, which version of Orbited are you using? I've
tried 7.10 and currently am using latest source code from bitbucket.
Have you modified anything? What are your settings like? I am
definitely setting the document.domain correctly in the parent/main
website.

Thank you.

[Dmitry Utkin]

Hi Bjorn,

other browsers are ok with this setup as I understand?
Can you see any errors(security?) in js on your page?
Are any of socket callbacks are fired (onopen, onclose)?

I've solved all the security problems by proxying orbited with nginx,
no document.domain fixes(which break some other things) are needed.

> --
> You received this message because you are subscribed to the
> Orbited discussion group.
> To post, send email to
>    <orbite...@googlegroups.com>
> To unsubscribe, send email to
>    <orbited-user...@googlegroups.com>
> For more options, visit
>    <http://groups.google.com/group/orbited-users>

[tejas]

Hi Bjorn,

Yes, I had trouble getting IE to work cross-domain in 7.10. I'm
running my site on www.domain.com, while orbited is running on
stream.domain.com. I did some patches to get it to work.

Essentially, for IE7 and below, I changed the JS to use long polling,
instead of iframe streaming. I could have done this for IE8 also, but
instead decided to go for XDomainRequest streaming (i prefer streaming
over long-polling, and IE8's cross-domain version of XmlHttpRequest,
XDomainRequest, supports streaming like Xhr does in Firefox).

I also had to throw in a bunch of document.domain = 'domain.com' all
over the place (see below), and the Html file that is going to be
running the streaming.

Here are my patches:

JavaScript:
http://66.81.238.4/common/javascript/streaming/orbited/orbited.js (you
can do a diff against the original orbited.js to see what has changed)

Server-side stuff (I think these are reverse diffs):
[root@hurricane static]# diff xsdClose.html xsdClose.html.bak
2d1
< document.domain = 'domain.com';

-------------------------------------------------------------------
-------------------------------------------------------------------

[root@hurricane static]# diff xsdrBridge.html xsdrBridge.html.bak
8c8
< document.domain = 'domain.com';
---
>

-------------------------------------------------------------------
-------------------------------------------------------------------
#Write 2kb of whitespace instead of 256 bytes, and set Access-Control-
Allow-Origin header to allow cross-domain requests (of course, make
sure this meets your security policy before setting this value to '*')
[root@hurricane transports]# diff xhrstream.py xhrstream.py.bak
16,18c16,17
< self.request.setHeader('Access-Control-Allow-Origin', '*' )
< # Safari/Tiger may need 256 bytes, IE needs 2KB
< self.request.write(' ' * 2048)
---
> # Safari/Tiger may need 256 bytes
> self.request.write(' ' * 256)
50c49
< self.request.write('x')
---
> self.request.write('x')
\ No newline at end of file

[Bjorn Tipling]

Thank you for your response, replies are below.

On Jul 1, 10:12 pm, Dmitry Utkin <dmitry.ut...@gmail.com> wrote:
> Hi Bjorn,
>
> other browsers are ok with this setup as I understand?

Yes.

> Can you see any errors(security?) in js on your page?

I get a "Permission denied." when attempting to access variables in
the global scope and "Access denied" if I attempt to acces the
parent.window.document object.

> Are any of socket callbacks are fired (onopen, onclose)?

Not sure, how would this help me?

>
> I've solved all the security problems by proxying orbited with nginx,
> no document.domain fixes(which break some other things) are needed.
>

I hope it doesn't come down to this as this would require a lot of
infrastructure change. So you proxy domains you also cannot get
different subdomains to work?

[Bjorn Tipling]

Awesome, I will give this a try right now! Thank you.

On Jul 2, 2:32 am, tejas <tejas....@gmail.com> wrote:
> Hi Bjorn,
>
> Yes, I had trouble getting IE to work cross-domain in 7.10. I'm

> running my site onwww.domain.com, while orbited is running on

[Bjorn Tipling]

This worked! Awesome, thank you. :)

On Jul 2, 2:32 am, tejas <tejas....@gmail.com> wrote:

> Hi Bjorn,
>
> Yes, I had trouble getting IE to work cross-domain in 7.10. I'm

> running my site onwww.domain.com, while orbited is running on

[leon]

Hi tejas,

I used your fix (in fact I had already added the document.domain stuff
all around the place where IE complained - but apart from that, all
changes you provided were just crucial and yet far beyond what I'd
ever try. I guess we're all pretty busy lately (I know I've been truly
absent) but it would it be possible to post a page on our home with
the modified pack of your JS files (maybe with some comments)?

Thanks,
Leon

On Jul 2, 6:32 am, tejas <tejas....@gmail.com> wrote:
> Hi Bjorn,
>
> Yes, I had trouble getting IE to work cross-domain in 7.10. I'm

> running my site onwww.domain.com, while orbited is running on

[tejas]

Sure, give me a week. I'm currently travelling and will do this once I
get back.