http://localhost:8000 and http://localhost:8888 meets javascript security model

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

http://localhost:8000 and http://localhost:8888 meets javascript security model

Tim Murray

Hi all.

 

We are building a "prototype' SCORM compliant application where we will be

serving up content from a Seaside Application and running third party

web applications in an 'I-Frame' inside a seaside component.

 

Currently, we are serving up our components on localhost:8888 and the third party

software on localhost:8000.

 

It all works swimmingly until we tried to set up a javascript communication link

between the two.

 

What happened is we bumped up to javascripts security restriction.

 

https://developer.mozilla.org/En/Same_origin_policy_for_JavaScript

 

that prevents javascript from one domain:localhost:8000 interacting with  a document

from another domain: localhost:8888 event though they come from same physical box.

 

So, we are brainstorming how to serve both our Seaside components and 3'rd party software from

the same domain: localhost:8888.

 

We are tossing around the idea of a custom WARequestHandler and perhaps registering all third-party sofwware

to use that handler, but we are not that good with the guts of Seaside, yet.

 

Your thoughts?

 

thanks in advance.


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: http://localhost:8000 and http://localhost:8888 meets javascript security model

radoslav hodnicak
just put everything behind a web server like apache/nginx/whatever and use it as proxy

On Tue, Sep 21, 2010 at 8:16 PM, Tim Murray <[hidden email]> wrote:

Hi all.

 

We are building a "prototype' SCORM compliant application where we will be

serving up content from a Seaside Application and running third party

web applications in an 'I-Frame' inside a seaside component.

 

Currently, we are serving up our components on localhost:8888 and the third party

software on localhost:8000.

 

It all works swimmingly until we tried to set up a javascript communication link

between the two.

 

What happened is we bumped up to javascripts security restriction.

 

https://developer.mozilla.org/En/Same_origin_policy_for_JavaScript

 

that prevents javascript from one domain:localhost:8000 interacting with  a document

from another domain: localhost:8888 event though they come from same physical box.

 

So, we are brainstorming how to serve both our Seaside components and 3'rd party software from

the same domain: localhost:8888.

 

We are tossing around the idea of a custom WARequestHandler and perhaps registering all third-party sofwware

to use that handler, but we are not that good with the guts of Seaside, yet.

 

Your thoughts?

 

thanks in advance.


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: http://localhost:8000 and http://localhost:8888 meets javascript security model

Philippe Marschall
2010/9/22 radoslav hodnicak <[hidden email]>:
> just put everything behind a web server like apache/nginx/whatever and use
> it as proxy

Yepp, way to go. Or write the other application in Seaside ;-)

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside