Hi, François...
It still doesn't work...
I installed, on a server in my domestic LAN, an Apache Web Server by downloading the file apache_2.2.13-win32-x86-no_ssl.msi from http://www.apache.org/....
On the same server I have FMS3.
- I replaced the rtmp:// protocol with http:// protocol.
- When I type my URL in a browser, mySWF is Loaded in my web browser.
-If I change the line:
myLoader.load(new URLRequest("str"));
with
myLoader.load(new URLRequest("http://192.168.1.67/fms3/videocomm/BlocchiLogici.swf"));
I have this error:
*** Violazione della sicurezza sandbox ***
SecurityDomain 'http://192.168.1.67/fms3/videocomm/BlocchiLogici.swf' ha cercato di accedere a un contesto incompatibile 'file:///C|/Documents%20and%20Settings/TOSHIBA%20SATELLITE/Desktop/Tesi%20Magistrale/Progetti/VideoComm/VideoComm.swf'
but mySWF is Loaded....
the other your questions...I don't know what to say: what is an embedded Apache? And what is "train movie"?
Please, my friend, help me...
Emiliano.
Emiliano,
What I see wrong in your code is lines like this :
myLoader.load(new URLRequest("myParam"));
If you do that you try to load on your server a file called myParam. Try this :
myLoader.load(new URLRequest(myParam));
So you will load the file name your server sent to your client.
About the embeded Apache, when you install FMS the installer asks you if you want to install a bundled Apache server or not. If you do so you will find the Apache server inside FMS application files and it will be configured to proxy HTTP request to it. To be short, FMS listen on port HTTP (80) and Apache on the port 8134 (by default). When FMS receives an HTTP request it post it to Apache on the 8134 port on localhost and the Apache repsonse is sent back to the client. So if you need to load a SWF file on HTTP then this is how it is done.
The "train movie" is a FLV video that you can see on a mini-site delivered with FMS installer. When you install it by default your server contains on it's base adress, port 80, a HTML page where you can see the FLV video. It is a lovely country side upview with an old train passing by. When you read the FMS installer that is how you can verify your FMS and Apache server are up and running.
If you installed Apache after FMs you have to do 3 things :
change you Apache httpd.conf to make it listen to an other port than 80 (let's say 8134). Just add the line "Listen 8134" where the httpd.conf mention the "Listen" parameter.
change your FMS configuration to proxy the HTTP requests on your localhost, port 8134.
then stop FMS, restart Apache and start FMS so they don't get into a listening port conflict.
Check FMS documentation in the administrator guide to look where you can do that for FMS proxy configuration.
Cheers,
François