For the latest news and happenings in the IIS community over the past month, be sure to check out the February edition of the IIS Community Newsletter!
So you’ve written a new ASP.Net website, tested it locally in your development environment and you deploy it to your IIS server. Now you’re getting the dreaded 500 – Internal server error. What are you to do?
Sometimes you need to restrict traffic to your web site or reduce the impact from a rogue bot that is hitting it. Often, the first thought is to restrict that traffic at the perimeter firewall. While that is a good choice, the structure of your organization may prevent that from happening in a timely manner. Or maybe you are frequently making changes to the restrictions making that a cumbersome chore.