I am having trouble getting FontAwesome icons to show on Windows Phone 8.
Phone (HTC 8X): OK on the dev box (http), but not on the QA server (https)
Surface RT, Pro, desktop: OK on both servers
All devices use IE10. Both environments (Dev and QA) use IIS7. It seems that IE10 phone is somehow different from IE10 tablet/desktop in its treatment of downloadable fonts.
Has anyone else experienced this?
It was due to a missing MIME type. I was wrong about both environments using IIS7; The QA server uses IIS6. We added application/x-font-woff to the IIS configuration, and that fixed it.
UPDATE:
Add this to your Web.config to associate .woff files with the correct MIME type, so the server will know what to do when such a file is requested:
<configuration>
<system.webServer>
<staticContent>
<mimeMap fileExtension=".woff" mimeType="application/x-font-woff" />
</staticContent>
</system.webServer>
</configuration>
Related
I have Parallels Plesk Panel 11.0.9 for Microsoft Windows host. I tried to play some short video using several solution including: camtasia, videojs and google youplay. but all of them can't play back my video on host; I mean it's play and show on local and everythings is ok on local.
I using asp.net 4.5 on local and asp.net 4.0 on remote host.
I downloaded test video on videojs and upload it to my host, but I confuse that there is nothing play from only my windows host. Are there any tip for playback video from windows host?
Depending on the video type, control panel should have proper MIME type added.
Log into your Control Panel.
Under the Domains tab, click on your domain name.
Navigate on Websites & Domains tab.
Click on Show Advanced Operations.
Click on the Virtual Directories icon.
Navigate on Mime Types tab.
Click the Add Mime Type icon.
Enter the file extension and Content.
example:
Extension: .m4v
Content: video/mp4
Click OK.
Thanks to Mitesh Gangaramanifor answering but there is no content as video/mp4 so I had to deeper search and find an guaranteed solution for this problem.
Just go to web.config and add these tags between <configuration></configuration> tag:
<system.webServer>
<staticContent>
<mimeMap fileExtension=".mp4" mimeType="video/mp4"></mimeMap>
<mimeMap fileExtension=".m4v" mimeType="video/m4v"></mimeMap>
</staticContent>
</system.webServer>
Then save and upload it to your httpdocs. I hope I could help who people had this problem.
<resizer>
<plugins>
<add name="MvcRoutingShim" />
<add name="AzureReader2" connectionString="UseDevelopmentStorage=true" endpoint="http://127.0.0.1:10000/devstoreaccount1/" />
</plugins>
</resizer>
I am trying to implement image resizing in my Mvc4 application using "AzureReader2". I had installed all the nuget packages and modified webconfig file as above. It works fine when i tried to deploy on server. But locally it fails, it's says "The remote server returned an error: (400) Bad Request.".
Do any one faced the same issue, if so let me know the work around please.
The local storage emulator for Azure hasn't been updated. Microsoft is working on fixing this. This isn't related to ImageResizer.
http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/27/windows-azure-storage-release-introducing-cors-json-minute-metrics-and-more.aspx
"As mentioned above an updated Windows Azure Storage Emulator is expected to ship with full support of these new features in the next couple of months. Users attempting to develop against the current version of the Storage emulator will receive Bad Request errors as the protocol version (2013-08-15) is unsupported. Until then, users wanting to use the new features would need to develop and test against a Windows Azure Storage Account to leverage the 2013-08-15 REST version."
I have deployed my app to my IIS server. The javascript/css seem to work when I browse the webpage from the IIS server (although some of the css seems to not be loading as well). However, when I go to another machine and view the webpage from a client, none of the Javascript seems to be enabled. The links to the scripts are there, and when I type their path into the browser, I am able to retrieve the file (so it's not a permissions issue or a path issue). Yes the browser I am viewing the page from has javascript enabled (it's my dev machine where everything works if I'm working from visual studio).
Can anyone help me figure out what is happening here? Everything works fine in my dev machine.
Edit
Ok I have tried everything I can find on the interwebs. I have tried adding the 'bundle' module, removing then adding (as below), I have tried with and without 'runAllManagedModulesForAllRequests', I have tried enableing and disabling the
<compilation debug="false" targetFramework="4.5" />
Nothing seems to work.
<modules runAllManagedModulesForAllRequests="true">
<remove name="UrlRoutingModule-4.0" />
<add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" />
<remove name="BundleModule" />
<add name="BundleModule" type="System.Web.Optimization.BundleModule" />
<!-- any other modules you want to run in MVC e.g. FormsAuthentication, Roles etc. -->
</modules>
I just don't understand why IIS7 would be doing something different when you browse the website locally on the server and another thing when you browse the site on different machine?
Edit 2
Even more baffling. I figured there might be something wrong with bundling (some assembly not loaded correctly who knows) so to test the theory, I commented out all the bundling code on my layout and replaced it with hard coded links to the styles/javascript. Again, it works in development, it works when previewing on the server, but when you go to a client machine, none of the javascript seems to work!!! I've installed it on two different IIS servers now... still same problem!
Edit 3
Unbelievable. It looks like the problem is... drum roll. IE10. I am using integrated authentication so I was only using IE. Until I realised that chrome can prompt/pass credentials as well. So I opened the site from Chrome and no problem! I compared the html from my local version on my dev machine to the html coming from the server, and other than the fact that the URLs have an extra element in the path (the site is deployed to a virtual directory) the html is identical. So for whatever reason, IE has decided that it will not run javascript from my IIS server, but it will from every other website on the internet. I even used fiddler to double check that all of the css/javascript was being fetched and received (they are, even checked the temporary files folder after a clean sweep to see if the css/js was downloaded). So, as usual, IE is a piece of crap causing nothing but headache and misery. Now to figure out how to fix this (my organisation is 80% IE).
So for anyone out there who might run into the same issue and has to work with IE I solved the problem by adding this to my _layout.cshtml:
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
What this does is instructs IE to use the latest available rendering engine to process the html (in other words don't try to be smart and guess what my html is built for). So it essentially tells the versions of IE that have 'compatibility mode' to not use it.
For me this works fine because our organization is small and we are usually within one version of the latest release of IE. If the latest version causes issues, I can easy fix and deploy with no harm done. However, this IS NOT optimal for a general purpose website or organization with high numbers of users on a variety of IE browsers.
I came across this problem too.
I found was that Internet Explorer was set to "high" when browsing the internet when using our corporate network. Once I added my site to the trusted sites zone, everything worked.
You can check if your site in the Trusted Sites zone, but going to Internet Options -> Security -> Sites
We have a website developed in vs2005 with framework 2.0.
The website works fine in all browsers unless IE10. The response.redirect doesn´t work and some buttons throws javascript errors.
If a force the explorer mode to IE10 compatibility view works fine, but we don´t want to tell all our users to force manually.
Anyone have the same problem?
Thanks a lot and best regards
I solved a similar problem by inserting the App_Browsers map into the root map, containing a browser file BrowserFile.browser with the code:
<browser refID="Default">
<capabilities>
<!-- To avoid wrong detections of e.g. IE10 -->
<capability name="ecmascriptversion" value="3.0" />
</capabilities>
</browser>
Try it:
Open your website in IE10
Tools > Compatibility View Settings >
Click in Add to your domain website >
Close
Reload your website.
It´s worked for me.
There is a bug in the browser definition files that shipped with .NET 2.0 and .NET 4, namely that they contain definitions for a certain range of browser versions. But the versions for some browsers (like IE 10) aren't within those ranges any more. Therefore, ASP.NET sees them as unknown browsers and defaults to a down-level definition, which has certain inconveniences, like that it does not support features like JavaScript, CSS etc.
Try the fix given in the below link. Worked fine for me.
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
I am moving a site from IIS6 on one server to IIS7.5 on another.
This site was not writen by me, and from what I can tell, they use custom handlers to get around the AJAX limitations of the day.
I copied the code from the old server to the new (pre-compieled) and everything works except the "AJAX" stuff. There are several calls in the code to ashx files. These calls return .js files. On the old server this works great. Does not work on the new server.
In the web.config file I found the following lines:
<httpHandlers>
<add verb="*" path="*.ashx" type="AjaxPro.AjaxHandlerFactory,AjaxPro.2"/>
</httpHandlers>
For some reason this is not working in IIS7.5
Any suggestions are welcome.
Thank you!
I suspect this could be down to the configuration of the application pool managed pipeline mode. You can easily confirm this by changing the Managed Pipeline Mode for the application pool the site runs under to Classic. If this works and you want to continue to run in Integrated mode then you will need to add a handlers section to the web.config. This is different from the httpHandlers information you noted above.
The new handlers section should be in the system.webServer section. I'm sorry I do not know the exact setting for the item you note but you will need to include the preCondition="integratedMode" if you wish to run in integrated mode.