Tag Info

Hot answers tagged

14

Worked out these steps which fix the issue for me: Open IIS Manager Click the server name in the tree on the left Right hand pane, Management section, double click Configuration Editor At the top, choose the section system.webServer/security/authentication/anonymousAuthentication Right hand pane, click Unlock Section At the top, choose the section ...


10

The ASP.NET AppDomain is restarted whenever you 'touch' web.config. It's possible to turn off the File Change Notification (FCN) for a folder, but it's usually not the best bet if you can help it. If you do turn it off, it just means that you need to manually recycle the app pool for changes to take effect. Prior to IIS7, only ASP.NET changes would cause ...


9

That's by design. The section of system.webServer essentially defines IIS itself. If you , you won't be left with anything. In applicationHost.config, you should have something like this: <modules> <add name="HttpCacheModule" lockItem="true" /> <add name="DynamicCompressionModule" lockItem="true" /> ...


7

You're using system.web. In IIS7, you should use system.webServer instead. This will block all types of files, not just ASP.NET files. For example, you can password protect jpg, gif, txt and all types of files. It would look something like this: <system.webServer> <security> <authorization> <remove ...


5

Found the answer after 4.5 hours of Googling! http://runtingsproper.blogspot.co.uk/2010/04/solved-breaking-parent-webconfig.html Basically taking advantage of <location path="." inheritInChildApplications="false"> <system.webServer> <!-- ... --> </system.webServer> </location>


3

The application that uses the web.config will restart when you change it, there's more info here: http://msdn.microsoft.com/en-us/library/ms178473.aspx I don't know of any way to prevent this from happening (and I'm not sure why you'd want to - perhaps you can provide some more details of what you're trying to achieve).


3

Configuration locking can happen at: Applicationhost.config (config string: MACHINE/WEBROOT/APPHOST) a Site Web.config file (MACHINE/WEBROOT/APPHOST/Web Site Name) Any App web.config file that (MACHINE/WEBROOT/APPHOST/Site Name/App Name) Locking a section (section: IIS configuration section, eg <asp>) lets you deny the ability to configure those ...


3

You can use the Location nodes on the Web.config. Here is a detailed explanation on msdn ; in a nutshell: <location path="Subdirectory"> <system.web> <authorization> <deny users="*"/> <!-- Denies all users --> </authorization> </system.web> </location> <location path="Public_Directory"> ...


3

You need to use the httpErrors element for IIS 7. <configuration> <system.webServer> <httpErrors errorMode="DetailedLocalOnly" /> </system.webServer> </configuration> http://www.iis.net/ConfigReference/system.webServer/httpErrors


3

FYI - In ASP.NET 2.0 you can use the built in Health Monitoring Events to log application restarts along with the reason for the restart. This will enable you to clearly document when and how often it occurs. This is accomplished by editing the master web.config for the machine. For more information: ...


3

[JUST A NOTE] I know this is an old one but this still deserves to noted. Scott Forsyth - MVP answer is incorrect. The ASP.NET AppDomain is restarted whenever you 'touch' web.config. This is wrong. Whisk answer is the most technically correct & complete answer as it includes a link to the MSDN that includes one important detail: When an ...


2

ASP.NET uses a heirarchy to determine which web.config file gets used. There is a machine.config with global system values, then each website has a web.config in it's root, and each virtual directory uses it's own web.config files. We run multiple asp.net applications on the same server using a combination of multiple websites setup in IIS and many virtual ...


2

The answer is no. The reason for not using same machine keys is that developers should not see production environment secret keys. If you have an ex-workers or external consultants, you can't guarantee that they won't spread the development code to somewhere. In wrong hands, the keys make it easy to attack to the servers. Here is a nice link.


2

Open the full URLs of the source files (...ScriptResource.axd...) in a new browser window. You should see some JavaScript content. If not, the asp.net ajax components are not correctly installed. Sys is not defined indicates that the Ajax client side component is not there, the sys class can not be found. If you are using .net 3.5 it is part of the ...


2

After a fair bit of research, it is 'locked' by default at the application level. As such, it needs to be 'unlocked'. this can be achieved via the command line or via the (extra download) iis7 admin tools. eg. appcmd set config -section:urlCompression /doDynamicCompression:true Refrences: Changes to Compression in IIS7 Dynamic Compression HowTo


2

Pay close attention to the fact that the IIS 7.x web.config setting of noCompressionForProxies="false" Is not honored at the web.config level. It must be set in C:\Windows\System32\inetsrv\config\ApplicationHost.config like so: <httpCompression directory="%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files" noCompressionForProxies="False"> ...


2

Try this - <configuration> <system.webServer> <httpErrors errorMode="Custom" defaultResponseMode="File" > <remove statusCode="404" /> <remove statusCode="500" /> <error statusCode="404" path="404.html" /> <error statusCode="500" path="500.html" ...


2

Scott, can you append this into your answer? Here is what I did based on what Scott said: Opened applicationHost.config in %windir%\system32\inetsrv\config. Note that in 64 bit Windows Server 2008, you'll need to edit the file with a 64 bit editor (the native Notepad will do, but Notepad++ won't be able to find the file). See here for more information ...


2

I hope it is not too late to help. I got this issue today and fix the problem editing de following ApplicationHost.Config XML node: httpErrors lockAttributes="allowAbsolutePathsWhenDelegated,defaultPath" Remove that ",defaultPath" and restart you IIS (iisreset). I hope its helpfull.


2

i think this can solve your problem. place this web.config in directory that contain target directory : <configuration> <system.webServer> <security> <requestFiltering> <hiddenSegments> <add segment="target directory name"/> </hiddenSegments> </requestFiltering> </security> ...


2

For the appSettings and connectionStrings nodes in web.config you can move these into separate files outside of web.config. In your web.config you would have: <appSettings configSource="appsettings.config"></appSettings> and then a new file appsettings.config: <?xml version="1.0"?> <appSettings> <add key="foo" ...


2

The reason is that you have two web sites targeted on the same physical folder. And there exists an inheritance in web.config. http://vmsomething is the parent and http://vmsomething/my_application_virtdir is its child. The child web.config inherits all elements from its parent. And the web.config usually is not designed to work in such scenario. You can ...


2

Add a MIME type to the IIS config for the .notebook extension. You'll have to find out exactly what the mime type is to use. Maybe application/x-smarttech-notebook.


1

No, according to the documentation, isapiFilters can only be defined on the server or site level. You may put the 32bit Application into its own site and then URL-rewrite every request for it from the main site. But that may result into more problems/work depending on your application.


1

Have an external service like Pingdom send a request to your site at whatever interval you want. Just make sure it is in fact an HTTP GET request to the URL. That should force the server to run the application. Lastly: Switch your web host provider, it will save you lots of headache down the road. I personally recommend DiscountASP.net. Great and cheap ...


1

Press Windows+R and paste: notepad %systemroot%\System32\inetsrv\config\applicationHost.config this will bring up the main configuration file for IIS: Most changes you are making in the IIS UI that don't make it into your web.config are saved here. Towards the end is a 'handlers' node that defines how the various file types are handled, all extensions ...


1

Should Use cacheControlMaxAge="0.00:01:00" instead of httpExpires="0.00:01:00" but the latter does not throw an error, just doesn't work.


1

There may be another way, but simply you can - create a local user under Windows, - add them to a local user group, - remove anonymous access to the folder containing the web site and - change file permissions to only allow access to members of the local user group For the IP whitelist, there doesn't appear to be a way to override basic auth by IP address. ...


1

When using Windows Authentication, the remote EC2 instance needs to authenticate you against your local PC or domain. Unless you have some kind of VPN or something set up, that won't work. Switch to using SQL authentication instead. You'll need to specify by user id and password in the connection string. Make sure port 1433 is open in your security ...


1

I think your problem is a pure WordPress settings issue. The rewrite rules from your post are only important for incoming requests. I.e. they rewrite the URL from an incoming request to the index.php page. They are of no importance for any URL's generated by WordPress and that's clearly where your problem is. My guess is that you have not properly ...



Only top voted, non community-wiki answers of a minimum length are eligible