Let IIS support Flv detailed setting method Step


The majority of domestic Win2003 hosts, FLV format file upload server can not play, the default is not specified output FLV format, although FTP can be seen, but can not pass http If you visit, you will not be able to play it. The reason is that WIN2003 enhances MIME authentication for IIS6, and all unregistered extended file formats display 404 errors. Manually add the MIME mapping relationship to the HTTP header->MIME in the IIS site attribute. The MIME type: video/x-flv extension: .flv can be played through the Flash7+ client Load. "Virtual host does not support Flv format file" problem: For example, your Flv file name is 1.flv, create a directory named "ldv; Format the file, rename it to: index.htm, and that's it, the file name and address in the player remain intact. Let IIS support the detailed setting method of Flv: IIS-->Website--->Properties--->HTTP Performance--->MIME Type--->New: Extension: .flv MIME Type: Flv-application/octet-stream

Recently, I have been tossing a new project, using php+mysql to achieve a report statistics function similar to EXCEL. The development process is difficult. One of the problems about FLV video files cannot be played. Although it is not complicated, I personally think it is necessary to share the solution. You may also be worried about it.

With the rise of major video sites, FLV format video files are also well known. According to the project requirements, you need to put FLV format video files on your own server. The first time I touched the FLV video, the truth was quite fresh. However, the problem also followed. The FLV video could not be played, and the status was always prompted. Checking the embedded HTML code is also correct. This is a bit of a sigh, think about it, upload the video directly to the potato, Youku class, and then refer to its links more convenient.

FLV video file can not play the solution

With Google, I found a lot of FLV format video files can not play. In fact, it is not complicated. The MIME type in IIS does not support the video file with the .flv extension. You can add it yourself. The following graphic tutorial will tell you the detailed solution!

1) Open IIS Manager, right click on your computer name -> Properties, find “MIME type”, as shown:

What is a MIME type? The MIME type is the type of the file in which an extension is set to be opened by an application. When the extension file is accessed, the browser automatically uses the specified

program to open it. It is used to specify some client-defined file names and some media file opening methods.

2) Do as follows: Click “MIME Type”->“New”->Enter Extension“.flv”->Enter MIME Type<quo;flv-application /octet-stream”-> OK, as follows:

3) Restart IIS Manager, refresh the webpage, is the FLV video file playable?

Tip: If you don't have your own server, it's a virtual host user, you can't add “MIME type& quoquo; to your computer. Don't worry, you can change the .flv suffix name of the video file to .swf, which is also playable.

The above is the solution for the FLV format video file can not be played, just to find the reason, the right medicine, or very simple. In the end, it will be well solved after encountering similar problems in the future. You must set the content 1: Active Server Pages, Internet Data Connector, RPC Proxy Service Extension, and server-side include files must be set to Allow Status 2 in the "Web Service Extension": "Website" 》Properties -> Home Directory - "Configuration -" Options - "Start Parent Path 3: & ldquo; Website & rdquo; - "Properties - "Services -" selected in the isolation mode & ldquo; WS5.0 isolation mode to run WWW service & rdquo; 4: Start - "Programs -" Administrative Tools - "Services. Find the RPC service, double-click - "Login -" to allow the service to interact with the desktop. In Windows2003 you can run asp Server.CreateObject("WScript.Shell") I want to use asp.net to do this program, and this problem has always existed in asp.netzh. So the use of asp in asp can achieve the function. I have not done it under asp.net, if you are interested, you can try it! 2: Solution: 1 Delete or rename the following dangerous ASP components:

Wscript.Shell, Wscript.Shell.1, Wscript.Network, Wscript.Network.1, adodb.stream, Shell.application Start - ------>Run--------->Regedit, open the registry editor, press Ctrl+F to find, enter the above Wscript.Shell and other component names and the corresponding ClassID, and then proceed Delete or change the name (I suggest you rename it here. If there are some webpage ASP programs that use the above components, just use the changed component name when you write the ASP code. Normally, if you are sure of you The above components are not used in the ASP program, or you can directly delete some of the ^_^ in your mind. Generally speaking, these components will not be implemented. After deleting or changing the name, iisreset can be activated after restarting IIS.) [Note: Since the Adodb.Stream component is used in many web pages, if your server is a virtual host, it is recommended to handle it. ] 2 About the File System Object (classid: 0D43FE01-F093-11CF-8940-00A0C9054228) is often said to be a FSO security problem, if your server must use FSO, (some virtual host servers generally need to open FSO function) I can refer to my other article on FSO security solutions: Microsoft Windows 2000 Server FSO security vulnerability solution. If you are sure you don't want to use it, you can directly register this component. 3 Directly deregister and uninstall these dangerous components: (I don't want to use the cumbersome methods of 1 and 2) Uninstall the wscript.shell object, run it under cmd or directly: regsvr32 /u %windir%\\system32\\WSHom .Ocx Uninstall the FSO object, run it under cmd or directly: regsvr32.exe /u %windir%\\system32\\scrrun.dll Uninstall the stream object, run it under cmd or directly: regsvr32 /s /u "C:\\Program Files \\Common Files\\System\\ado\\msado15.dll" If you want to recover, just remove /U to re-register the above ASP components such as: regsvr32.exe %windir%\\system32\\scrrun.dll 4 About using set in Webshell domainObject = GetObject("WinNT://.") to get information about the server's processes, services, and users. You can stop and disable the Workstation [providing network links and communications] in the service, that is, the Lanmanworkstation service. can. After this processing, the Webshell display process will be blank. 3 According to the above methods 1 and 2, after processing the dangerous components of ASP, use the asp probe of Ajiang to test it. "Server CPU details" and "Server operating system" cannot be found at all, the content is blank of. Using the Ocean Test Wsript.Shell to run the cmd command also prompts Active to be unable to create an object. Everyone can no longer be bothered by the ASP Trojan that compromises the security of the server system. Of course, server security is far from this. Here is just a few of my experiences in dealing with ASP Trojans and Webshells. In the next article, I will introduce you how to prevent others from executing commands such as net user on the server, anti-overflow attacks to get cmdshell, and the most to perform adding users, changing NTFS settings to terminal login, etc. Simple and effective prevention method.

Copyright © Windows knowledge All Rights Reserved