The information in this article applies to:
SYMPTOMS
When you attempt to play a URL involving server-side processing where the MIME type is generated dynamically (such as an ASP page or a CGI script), the URL may not be opened correctly by Windows Media Player or Internet Explorer. -OR- The file may be fully downloaded before playback, instead of progressively download, during which, playback occurs CAUSEIn certain dynamically-generated responses, the MIME type does not match the extension for the URL. This would be true of a CGI script returning an ASX file. Normally this MIME type is "video/x-ms-asf." Windows Media Player attempts to verify ownership of a file type before it will support progressive download or streaming of that URL. If Windows Media Player cannot determine if it should play back the file type in question, it will not progressively download the file. If Windows Media Player does not progressively download the file, Internet Explorer may not store the file, resulting in an error message. WORKAROUNDFor clients using Windows Media Player version 6.4 or later, add the following parameter to the URL for the server script: mswmext=.extWhere the .ext is the extension for the file type you are using. For example, "http://microsoft.com/sample.asp" would be "http://microsoft.com/sample.asp?mswmext=.asx," if sample.asp was expected to return MIME type "video/x-ms-asf". Similarly, for an HTML form performing a GET request to a Web server, you would add the following to the HTML form: <input type="hidden" name="mswmext" value=".asx"> STATUSMicrosoft has confirmed this to be a problem in Microsoft Windows Media Services version 4.0. MORE INFORMATION
Support for the "mswmext" parameter was implemented in Windows Media Player version 6.4. You may need to upgrade to this release in order for this workaround to be effective. Additional query words: netshow wms wmp
Keywords : |
Last Reviewed: August 12, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |