Since the path rewriting issue mentioned previously wasn’t a BlogEngine-specific problem, I was reluctant to invest a large amount of effort to solve the path problem if it would only fix BlogEngine.  As it turns out, I can pull a similar trick “on the way out” as the one being applied on the way in.  Instead of modifying hundreds of instances of path concatenations in the BlogEngine code, I wrote an HttpModule that “unwrites” the path that GoDaddy seems to be sending in. All that the module has to do is attach to the HttpApplication.PreRequestHandlerExecute event and then wrap another layer around HttpResponse.Filter.  This give the module a chance to tinker with the values that the page attempts to write to the output stream.  BlogEngine.NET itself uses this same method to add compression... which introduces an interesting ordering concern.  I’m attempting to “unwrite” text, so my module’s filter needs to be one of the first ones called — so that it doesn’t ... [More]