Showing posts with label iis 7. Show all posts
Showing posts with label iis 7. Show all posts

Tuesday, January 1, 2013

Display Classic ASP Errors in the Browser Using IIS7

Classic ASP works a bit differently then the .NET framework. To many administrators (like me), the subtle differences can be a bit of a nuisance. Tasks that are performed daily with .NET are just different enough with Classic ASP to force an admin to consult the Google Brain. If that's why you're here - don't feel bad and don't worry. We have all been there, and we have a solution for you.

This post will focus on error display using IIS7 and Classic ASP. In .NET, this is a simple matter of configuring the customErrors imperative in the web.config file. With Classic ASP, a bit of work needs fixin' within IIS Manager. Launch IIS Manager (Start --> Run --> inetmgr). Highlight your server name onthe left-hand menu. Then on the right side, you should be looking under the IIS heading. Select Debugging Properties and set the "Send Errors to Browser" setting to true. Back under the IIS heading, select Error Paged and then the 500 Error Page.Select Edit Feature Settings and click the checkbox for "Detailed Errors". That should be all you need.

It is possible that you continue to experience issues- where that is the case, there are problems with either IIS or your ASP install is broken. Feel free to email me or comment if you still have issues and we can figure it out.

Tuesday, April 17, 2012

Websockets and IIS7

So its been about 5 months since the IETF released the RFC 6455 proposal for websockets:

The websocket API is a protocol that allows for the bidirectional transfer of http/https data. This breaks down to a single initial handshake and then autonomous communication from both the server and client concurrently. With it comes a significant performance improvement (as only one handshake is needed, and client-side implementation gets much simpler) and a number of practical applications - I always think chat clients, but the applications are endless for web driven applications that require real time data transfer (HTML5 games that don't suck!)

Its no secret that websockets will not work with a standard IIS7 implementation. Http.sys is a greedy bugger, and gobbles up all connections listening on port 80. Even with WCF, there is no formally recognized workaround besides "wait for 8" and the native websocket/SOAP functionality that it will bring with it.

That being said, some folks may find a need to use websockets technology on an IIS7 server, and I found a neat prototype from Html5 Labs that can do just that: http://html5labs.interoperabilitybridges.com/prototypes/websockets/websockets/download

The protoype is WCF / Silverlight driven.

Haven't had a chance to test it yet, but I have a feeling this will come in handy in the future. Let me know what you think!

[EDIT: HTML5Labs deactivated the download to their prototype last month, sorry guys. I am not sure why - its not like 2008 is going anywhere any time soon. The good news is I am compiling some guides on using WebSockets in Windows Server 2012 here. For those developers who are not in a position to upgrade, it may be worth checking out SignalR as one alternative to websockets. SignalR relies on APM as opposed to WebSockets, and can be of benefit when establishing fast connections - it can be deployed on Server 2008 and using older browsers ]

RAT Bastard

Earlier this week, several servers I maintain were targeted by automated attempts to upload a remote access trojan (RAT). The RAT is a simpl...