I have just migrated from IIS 6/ SharePoint 2007 to Windows 2008 with SharePoint 2010. We had a control that servers content with .MHT files. In SharePoint 2007 it was simply able to open it within the same window. In SharePoint 2010 it is showing a "SAVE FILE DIALOG". So, how can I fix this so that IE automatically opens it just the way it does in SharePoint 2007 without showing a "SAVE FILE AS" dialog?
Thanks
Brute Force way:
Central Administration > Manage Web Applications > Select your Web Application > General Settings > Set the File Handling from "Strict" to "Permissive"
There is a better way, but I don't have the link right now (will need to look it up again tomorrow). Essentially through a PowerShell command you can whitelist file extensions rather than setting the entire web app to Permissive.
Related
I upload images to the server via ajax which are saved in the directory wwwroot.
After this operation page auto refreshing like "browser link".
How can I disable tracking for change in some directories in wwwroot ?
Thanks!
It seems you are talking about the Browser Link and not Browser Sync which is an extension in Visual Studio for ASP.NET projects.
Unfortunately, in either of them, there is no way you can disable it for specific directories. You can only disable them completely. Click on the link given above to learn more on that.
When I use the "publish web site" feature in visual studio 2008, it automatically places a app_offline.htm on the web server while it is pushing the files up. If you navigate to http://MyWebSite.com/somepage.aspx you will see the application offline page, which is good.
However if you navigate to http://MyWebSite.com you will get a directory listing denied error message.
Is there any way to correct this behavior?
What is the default document? If the default document is a .htm(l) file, which won't pass through the .NET ISAPI (If you are using IIS 6 or less or on 7+ in classic mode), then .NET won't have the chance to intercept the request and display the offline page.
Since it is not placing any web.config there to allow viewing pages it will give that error. You can set a default page in IIS though.
I have an internal web page that I have an iframe with the source pointing to a webdav folder. This allows the user to drag and drop a number of files on the iframe window which a button on the main page then kicks off a server side task to process the files.
I am looking for an alternative that will allow me to drag a group of files and drop them onto a target area of a web page which will then upload them to the web server.
Ideally this would be in ASP.Net 2,3 or 4.
Any suggestions?
TIA
J
I ended up using multi file upload Silverlight component. It works like a charm and I believe it is available on codeplex.
We have 3DXML files in IIS6.0 virtual directory; we wanted to open those on browser using ASP.NET 2008, when user click on a button. How could we do that, any idea!
Thanks
Have you looked at this 3D XML viewer.
It has a standalone and browser component.
I'm having this problem on a new cruisecontrol.net install running on Windows Server 2003 where I cannot browse to http://localhost/ccnet/default.aspx.
I can, however, browse/open .html files, just not .aspx pages.
The errors I get when trying to access .aspx pages are:
In IE: "Internet Explorer cannot
display the web page".
In Chrome: "Error 101:
ERR_CONNECTION_RESET".
I've done the aspnet_regiis thing and double-checked my web extensions. Web extensions show as "ASP.NET 1.1.4322" and "ASP.NET 2.0.50727", both set to "Allowed".
Any ideas?
You may get a Page cannot be found message when you browse aspx pages in a Windows Server 2003 environment.
That is because in Windows 2003, all the webservice extensions are "Prohibited" by default to ensure security.
To resolve this, do the following steps:-
From your Run command, type inetmgr and press enter.
Expand the appropriate nodes in the IIS to locate the "Webservice Extensions" Node
Click on the same.
You will find a list of "prohibited" extensions in the right.
Click on ASP.NET and "allow" it
That should resolve this issue.
This applies for Windows Server 2003, IIS 6.0 environment.
pulled from: Link
I figured it out... sort of. The solution (if you want to call it that) was to uninstall IIS, reinstall IIS, then reinstall Windows 2003 Server SP2. After that, works perfectly.