For some reason when I make a change to IIS 7 now it generates a web.config file for things like mime types and directory browsing. I do not remember every seeing this behavior from IIS before so I am wondering how I can turn it off. I do not want the web.config file to be generated much less used in the site I am developing for IIS. Please advise as to disable this and force IIS to make these changes without generating the web.config.
Thanks in advance,
Ed
Since IIS 7.0 the IIS has started to store the settings in web.config. which is very handy if you are going to change the hosting of your domain. All of your application level settings will remain in one place.
If you are a developer, the web.config can perform a lot of things that can ease your life. There is no harm in keeping this file on server.
Related
I'm trying to setup Forms Based Authentication in IIS 7.5 with ColdFusion 10. It's somewhat working but not prompting for ColdFusion pages. Yes, I did enable the Integrated Pipeline to force auth on all files. Then, I disabled auth on the two ColdFusion Virtual Directories. Not doing so caused a redirect to /jakarta/isapi_redirect.dll instead of the real/calling page.
So the interesting thing is that ColdFusion files (.cfm .cfc) seem to get past the authentication because they are processed by the un-authenticated Virtual Directories.?. (even though the requested page is still the called page..)
Any thoughts would be appreciated. Thanks!
Well, I've found a workaround but I'm not sure it is the right/best solution. Basically disable Anonymous Authentication EXCEPT for the ColdFusion Virtual Directories and the folder that contains the login page. Open to any other ideas anyone might have.
Now, to get Forms Based Authentication using ColdFusion with .NET objects... :)
I found that the FormAuthentication iis module was not being called for isapi_redirect.dll(jakarta pages) probably because of the precondition preCondition="managedHandler" that's default on FormAuthentication module.
Adding
<modules runAllManagedModulesForAllRequests="true" >;
in web.config allowed things to work as intended.
Enabling Trace Logging for Failed Requests were indispensable in figuring this out. This was with win2016/cf2016/iis10.
I inherited a mess of servers which host multiple applications on IIS6, protected by R6 SiteMinder. The environment is soon going to R12, and we have also received some new servers with IIS7.5. (Lots of change, all within the next 60days.)
I am not an expert, and so am having trouble with some of the more detailed steps of configuration. Thus far, on the new server I am able to create and apply SiteMinder to the DefaultWebSite (and everything contained within), and any custom Sites that I create. Unfortunately in our environment, it is already set up with a handful of applications that live underneath DefaultWebSite, only some of which we desire SiteMinder protection.
In IIS6 I was able to simply add a site to SiteMinder authentication by applying the ISAPI6WebAgent.dll in the wildcard mappings. In IIS7.5, this does not seem to work. I follow the specific details in the installation manual and it seems like it is either an all-or-nothing situation: everything under DefaultWebSite is protected, or nothing is.
This will cause a SIGNIFICANT amount of additional work in my environment (and it also means upgrading in place is not possible, so all applications that require SiteMinder authentication will need to be migrated in the next 60 days.) Is there ANY workaround for this? Google has not provided me with any solutions, and my SiteMinder team is claiming "it is no longer possible with IIS7.5" to keep the environment the way it is currently set up.
Any and all help appreciated.
For those that care, if you are running under an Integrated App Pool, you can simply add and remove the SiteMinder modules to control which sites are protected by SiteMinder. This DOES work on apps below a virtual directory - and using the config files you can both inherit protection by default, or have it unprotected and add it later by simply "Configure Native Module" and adding it back.
It looks like my server has ASP disabled because when trying to view an ASP file its source code is shown in the browser. After doing some research I've heard I can enable ASP on my server using IIS - is this correct? I've set up my website in IIS as far as I could; it's not asked me for FTP details or anything so I don't know how it's going to 'install ASP'... I've enabled ASP via the Control Panel so it appears within IIS, but don't know where to go next. Am I headed in the right direction?, could anyone give me some advice as I'm not sure if I'm barking up the right tree. Many thanks in advance.
I just tried this on my Windows 7 Professional box. Once I added the feature using "Add Windows Features", and refreshed IIS Manager, Classic ASP just showed up in the handler mappings.
Make sure Enable Parent Path = true in behavior Section of ASP in IIS.
Go into your programs > windows features. Find IIS, and go to www services. You should see ASP there. You may have to enable it in IIS as well - you haven't mentioned what version of IIS you're using (or OS), so I'll leave that up to you.
I am working on one website which is developed in .net. I have uploaded .htaccess files but its nt working.
Is there any new idea for that? I want that my site will be crawled with www.
Thanks
.htaccess is not just for PHP.
It's a configuration file that's read by the Apache HTTP server. So if your application is not running on that server, then that file will not have any effect.
.htaccess and PHP are orthogonal. One is a configuration file for Apache; the other is a scripting language. More than likely, you're using Microsoft's IIS server, not Apache.
The .htaccess file is a configuration file for the Apache web server, and is not dependant on PHP. It typically contains settings relating to web site user permissions, friendly URL definitions, etc.
It can, however contain configuration settings for PHP, if you have settings which are in the server's PHP.ini file that you want to override for this specific web directory.
There are many reasons why a .htaccess file may not work -- it can be broken by some very subtle things, and a faulty .htaccess file will normally cause the whole site to stop working completely, regardless of what the error is.
In this case, the browser will usually simply show an error 500, without much useful information to help you debug it. But there will be more helpful debugging data in the server error log.
If you still struggle with it, you should post your .htaccess file here so we can help you debug it.
However, as #Tomalk says, if you're developing a .NET site then you're probably not using an Apache web server; you're probably using an IIS server. In that case, there are entirely different ways of setting the configuration for the server, and it won't know what to do with .htaccess file.
Trying to copy a website to a new server as the old one is dying. :(
I tried copying over the files and setting it up manually, but some specific user accounts needed to be used and the guy who set all this up left the company nearly 5 years ago. And is even worse at documentation than I am.
Anyway, at that point the ASP pages were serving, but getting errors. Ok, fine... I went back and exported the configuration from the old server (lucky that worked at all) and created a new website from that config on the new server. On the new website, from the config file, the ASP pages are giving 404 errors.
The Active Server Pages extension is enabled, and I can actually get the asp pages to serve from another website on the server... so I'm thinking it's something at the website level. No idea what though.
Any ideas?
Back when I was doing classic ASP development we used Parent Paths. This is at the top of your ASP file you'll see something like;
<!--#include file="../../resource/includes/MSSQLconnection.asp"-->
This isn't enabled by default in IIS. It may not be answer but worth looking at. But was a long time ago now.
Hope this helps,
Mike
404 is a file not found error.
Start by checking you can access a 'hello world' HTML file in the folder using http: //localhost/path/toyour/HelloWorldFile.htm
Hello World
is all you need in the file = you don't need to bother with any HTML markup to test what we're interested in.
This will check that your virtual directories, application settings etc are correct before you move on to the Active Server Page settings.
Once you've got your paths sorted out and you know you are looking for your application in the correct place move on to a 'hello world' ASP file
<%="Hello World"%>
is all you need in that file!
You ask about settings in IIS which will stop ASP from working. These come to mind as the most obvious.
Depending on the OS (or more specifically the IIS version) you may also need to activate ASP pages.
These instructions from msdn cover Windows 2003 (IIS6) and Windows 2008(IIS 7.x)
If you can get your hello world script working you can move on to debugging your application.
It will be a great help when debugging the application if you can see what's going wrong so I recommend that you turn off friendly error messages if you are using Internet Explorer. Also set IIS to pass error messages on to the browser
see:
http: //learn.iis.net/page.aspx/564/classic-asp-script-error-messages-no-longer-shown-in-web-browser-by-default/ --excuse the link formatting but SO's newbies can't post more than 2 hyperlinks in a message was getting in the way of me trying to be helpful and earning enough rep to post more!
(that may only be relevant to IIS 7.x I don't have an IIS6 installation lying around to refresh my memory.
Make sure you are browsing your application on the server using http: //localhost - this should ensure you see any errors
Good luck