I have a Flash player application that plays movies and, if I give it a relative URL, it works fine in the IDE (Flash Pro CC) and on the webserver. The problem is that I need to play a movie that is on the webserver, but in a folder outside of the website (outside of root).
I tried passing the filename as such: "file://C:/Users/MyName/Desktop/Movies/mymovie.mp4". This works fine in the IDE - I can press Ctrl+Enter and the demo works. It also works fine if I test it in a browser (Ctrl+Alt+Enter). But via my IIS server (which is on the same laptop as the IDE), given the same filename, the same application won't play (although, it will play if given a relative URL to a file within the website). Any ideas why not, or what's going on?
These work as they should, in IDE or browser:
netStream.Play("Movies/mymovie.mp4");
netStream.Play("http://localhost/Movies/mymovie.mp4");
This works, only in IDE, not in browser:
netStream.Play("file://C:/Users/MyName/Desktop/Movies/mymovie.mp4");
I see now, though, that the Flash SWF is on the client browser, and that's the problem. Is there a way to reference a file back on the server, but that sits outside of the website? Maybe something similar to this method: https://forums.adobe.com/thread/838338, but that works for .mp4 files?
Related
After thinking about this for 2 weeks, I have to ask this question.
I've created a NW.js app that works smoothly and nice on 7 different laptops and PCs. The app shows html videos and contains a bunch of javascripts, I've got deloped since 2 years. Alls this works fine on every laptop/PC.
Here comes the problem:
On one laptop the app works, too, but the app isn't able neither to show HTML frame contents nor to execute js scripts from a specific web domain. This only occurs with a specific domain (that I'm the owner of).
The strange thing is, that this happens only on one laptop.
The laptop uses the same internet connection as some other devices. I reinstalled the app, deleted all subfolders from the app folder, but the error is back. In the frame I see the silly message, that the website is down or moved.
You likely have a system-wide proxy configured or possibly some AV software installed on that laptop is blocking that site. Attempt to access the same URL through another browser (Chrome, Edge, Firefox, etc.) to confirm.
Could be related to your hosts file.
C:\Windows\System32\drivers\etc\hosts
That is a plain text file without an extension. You can put URL's or IP addresses in it and it will block any access to them globally on the computer.
Though Sysrage is probably right, it's more likely that you just have some AV/firewall/security software blocking stuff it shouldn't (happens all the time, they can be "over protective" sometimes)
If it is something related to your NW.js install, and it isn't happening on other machines (so you know your app code is correct), then you could try deleting the app data folder for you app. To find it's location on the computer run console.log(nw.App.dataPath). It should be something like:
C:\Users\YOUR USER NAME\AppData\Local\YOUR APP NAME
You can just delete the whole folder (make sure your app isn't running first). Then the next time you open your app it will recreate that folder (it's a chromium thing). Things like saved passwords or dev tool customization or spellcheck dictionary modifications are stored in there. So maybe there's just something funky that needs cleared out.
I have a JSF application that uses Primefaces 7.0. Some of its pages use the p:media component to display the content of PDF files. When installed on a remote linux server, the application does not show the content of the PDF if used with Firefox 67.0. It works fine with Chrome and IE. And it works perfectly on my Windows 10 PC, even with Firefox. To make it even wierder, inspecting the element makes it visible in my laptop, but not in my desktop computer. Has anyone else a similar problem? Please advice.
EDIT 11/11/2019: Today I learned that the problem occurs when using https instead of http. Therefore, it doesn't really matter that the server is remote; what happens is that on our remote (and public) server we use https
I have a Red5 application that I inherited from a previouse developer and I am trying to get it running correctly. I am able to start the Red5 server and stream video files from my /webapps/myapp/streams/ directory. I am able to test this by going to http://localhost:8080/myApps/streams/testVid.mp4 and the video plays normally.
However, I need to be able to stream my videos from any directory in my file explorer. The application already has a Application.java, a CustomFilenameGenerator.java, the needed bean for CustomFilenameGenerator in red5-web.xml and a playbackPath and recordPath in my red5-web.properties file.
From my research it seems like the previous developer that worked on this project was probably able to get the streaming working from a custom path, but I am not sure how to get it running.
Assuming that everything with the application/configurations is correct how do I actually test it, if the files I want to stream are in C:\Users\myUser\Desktop\StreamRecordings?
I have tried going to http://localhost:8080/myApp/StreamRecordings/testVid.mp4 but I get 404 error (probably since StreamRecordings is not in a myApp subdirectory.
Thanks!
At present, I start up red5 in linux command line ./red5.sh and it runs the script. Then I go to http://localhost:5080 demos page to set up my camera and audio input and all works fine in testing the stream both on demo page and in swf of my webpage.
Question is, do I need to include some java and/or action script for the swf player to
bypass the red5 demo page so I can directly connect my input and stream in the code of the page? Also so only logged in webpage viewers can connect?
Overall wondering if there is a way of hiding the server stream from anyone not logged in to view it on my site? I understand in webapps folder somewhere there is the hosts list of IP but it would be impossible to know the IP of the viewers as opposed to unwanted viewers or bandwidth stealers.
I am trying to set up a site for poetry readings and make it so readers can record live to my server and then logged in viewers can view from my website. I am trying to figure out whether I must have that red5 page open and if that doesn't pose some kind of risk.
Found my own way of doing this just by removing and renaming files and folders.
If you go to usr/local/red5/webapps here lies all the directories for viewing when you go to default port 5080 so I simply installed the applications I needed and then took everything out of there except those applications I wanted and needed to run. I took out all and placed it in a folder in /var directory named it red5_movedstuff in case I want access to further applications later on.Then I renamed the applications I am using in webapps folder and kept admin folder to access them but I renamed my applications and had to importantly rename also in WEB-INF for each application name change.
Now if someone goes to myip:5080 they get a blank page and by changing names of applications I've hidden my directories beyond that including list of streams.
I have created a web application in that application i have added two folder. one is admin folder and under admin i have added a upload folder. In upload folder i have three different audio's. And also i have imported DLL for Windows media player. Through this media player im able to play the audios in local host.
By giving Direct path like MediaPlayer1.Filename="C:\User\sam\waka.mp3"
But when i host the website im getting problem the page is getting refreshed but the audio is not getting played.
I have tried this path Server.Mappath(".\.\upload\waka.mp3")
and Server.Mappath("~\admin\upload\waka.mp3)
the above both paths are not working when i host the website please reply.
It's still a bit unclear, but it sounds like there's some kind of audio player in your website (an ActiveX control or something?) that's trying to reference a path on the server as though it were on the client that's loading the page. Naturally, this will work on your development machine because the client and the server are the same thing.
What's actually being rendered on the client side? What happens if you reference the audio file by its URL rather than its file system path?
Or are you trying to do something different than what I describe? Are you actually trying to play the audio on the server when the client accesses the site?