Working in IIS7.0(7.5.7600.16385) on Windows Server 2008 R2
Trying to get a video of the type .MP4 to play on a webpage.
IF the URL is specified using the actual server path, the video will play:
\\myproductionserver\wwwroot\Video\Activevideos\videotestpage.html
This is true for our production and development servers.
However if i use the actual URL:
http://example.com/Video/ActiveVideos/videotestpage.html
...it will not play
Per various information sources, I have added .MP4 as video/mp4 to my IIS MIME Types (via GUI).
Nothing works.
Thoughts on getting this to work?
==================
UPDATE:
I went to HTML5TEST.com and it says under the video section that MPEG 4 is not supported. following some suggestions from this post for IE 9 HTML5 - mp4 video does not play in IE9
I replaced my video tag with the one that shows "Your browser does not support the video tag."
When I ran my page, Your browser does not support the video tag. came up.
So...what is that telling me? Especially since if I execute the url using the actual server paths, it works?
Got it to work by putting the following in the page:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9" /
You can add this code in the webconfig:
<remove fileExtension=".mp4v" />
<mimeMap fileExtension=".mp4v" mimeType="video/mp4v" />
After restart App pool and open you website or web app
Related
I'm working on making a client's blog site AMP-friendly and I'm running into an issue with their audio posts. It's just a simple WP site where they are uploading the audio files for the podcasts and I'm running into an issue where it says
Source must start with "https://" or "//" or be relative and served from either https or from localhost.
I don't see anywhere in their documentation that this is a rule. I have not run into this issue with other media types. Is there a fix other than setting up an SSL for the site?
No, there is no work around. You must use https for Audio. See here too.
I'm using IIS to serve mp4 videos. I get a 404 on mac/safari. It works in chrome and firefox on the same macs. The MIME is video/mp4 .
I've ran tests locally to rule out the video encoding, and the videojs. I've taken the request path directly as well, skipping the html and js, with the same results. Safari will not load the direct url to the video either.
I'm not sure where to look next?
It turns out Safari does range requests for media. IIS itself can handle this, but we are using mvc routing - and we didn't provide any handling for this. The solution is to build an action result that handles range request. We're pulling a solution based on this article
I'm using Orchard 1.7.2. I created widget with MediaPickerField for video file. On the front-end i trying to get this video by url (../Media/Default/Video/video.mp4) and play it using html5 video player. But i get 404 error when trying to load it. I tried fix it like here but after that i get 500 error. I got this errors only on video files and only on server. On local machine everything working fine.
Well, i fix it by adding MIME Type on IIS. There were no mime type for mp4. So i added .mp4 extension and video\mp4 mime type.
I’ve got a Classic ASP application running on IIS (6/7) servers. When a page is requested that won’t be accessible any longer, I want to send a Response.Status = "410 Gone" but still deliver some sort of ErrorDocument. It seems that browsers halt retrieving as soon as they get a 410.
Except for IE, all browsers display the same “The page you requested was removed”, so I guess it’s a server setting. In .NET, there seems to be TrySkipIisCustomErrors, but for Classic ASP, I’m actually quite confident it’s anywhere in the Error Pages feature in IIS Manager.
Can I tell my IIS to still deliver content, even when the actual URI is gone?
In your web application’s root directory, you have to add an attribute in the web.config file:
<system.webServer>
<httpErrors existingResponse="PassThrough">
…
</httpErrors>
<system.webServer>
With existingResponse set to PassThrough, the response will be delivered if an existing response exists. There’s a nice article on HTTP Errors at www.iis.net.
There doesn’t need to be an <error> element, especially none on status code 410 (but of course you may add one).
You could place a classic ASP page there that delivers the content and HTTP Status Code you want.
I tested this on IIS 7.5 with following code:
<% Response.Status = "410 Gone" %>
<html>
<body>
<h1>this is my content</h1>
</body>
</html>
Firefox shows the content as is, not a generic error page.
Update:
You will have to disable custom errors for this to work. You can do this by adding following line to your web.config (into section configuration/system.web):
<customErrors mode="Off" />
Otherwise, the default error page overrules your output. Classic ASP really doesn't seem to have anything like TrySkipIisCustomErrors.
I have soundmanager2 as player for mp3 sounds.
When I loading .swf file from same server as webapp its playing mp3 files normally
When I load .swf file from another server its not okay
The only change i added is:
soundManager.setup({
url: 'http://s3.amazonaws.com/mybucket/swf/'
})
In firebug>Net bookmark i can see that swf loaded but no mp3 load (when i click play in site)
I added crossdomain.xml but this not helped.
Worked according to this sample: http://www.schillmania.com/projects/soundmanager2/doc/getstarted/
Assume my webapp running locally at: http://local.dev
and swf served in another localapp running under http://local.media
so when i do:
url: 'http://local.media/swf/'
from local.dev app, its not loading nor playing.
Even for amazon it has to have crossdomain.xml :-\ even if i managed ACL well