This content has been marked as final. Show 4 replies
I have some new information: I have been trying to upload this application to two different servers; one is in my office (microsoft IIS 6) and a second one is a hosted account I have for a client (also microsoft IIS 6) and niether of them work.
I tried (just for the heck of it) to copy the bin-release content onto a linux server I have in my office and it works! I went back again and checked rights on the files on IIS and they look fine too. I made sure I gave all rights to the anonymous user account (IUSR_MACHINE NAME) and tried again with no luck. I don't think its a rights issue. There must be some settings on IIS for this to work. Any Ideas??????
Ok, I figured out what was wrong and I thought I should post the fix up here for all you folks who hopefully won't spends as much time as I have solving this.
Windows 2003 Server (IIS) does not know what mime type the flv files are. There are no direct errors at all when you try to stream them from within a flex application. Here is how to add the .flv MIME type in Microsoft Windows IIS
1.) Select the site to configure in IIS, right click and select "Properties"
2.) Under HTTP Headers Tab, select "File Types" and under the MIME Map section and select "New Type"
3.) Type ".flv" as the associated extension and "video/x-flv" as the content type.
4.) Select "OK" and you're ready to go.
This is very easy to do if you have control of your own server and you can configure IIS but I checked in my control panel for the clients hosting account and there are no settings like this to be found anywhere. It looks like I might have to ask the hosting provider to add this mime type on the server for me (bummer).
I hope this helps!
Sun of a .... I've been banging my head against the wall for a couple of months just trying to understand WHERE the problem might have been.
My solution then was to just use a streaming media server like FMS (since I also wanted seeking ability to the rather long duration of audio/video files).
I bow to you for pinpointing exactly what the problem is/was.
John Baranowski: You rock! Thanks a million! MS would've stopped supporting Win Server 2003 by the time I figured this out. Btw: The MIME type for f4v is video/mp4.