Do ASP.NET Integrated Pipeline settings cause Websense warnings on BlogEngine ?

Websense says Potentially Damaging Content - help!

As I wrote a few days ago, I've been having issues with Websense marking this BlogEngine.NET blog as Potentially Damaging Content. This kept me from accessing the blog from my day job, and made me wonder who else might be unable to read it. In particular, I worried that potential clients would encounter a Websense warning and reject me from consideration.

"Dude, where's my CSS?!"

Yesterday, I found that Websense no longer seemed to think my blog had "PDC". Unfortunately, when I tried to access my site, I only got the HTML. The CSS styles were not applied, making the site look like something out of the mid-1990s, complete with Times New Roman text and bright blue links.

New BlogEngine install, old problems

Last night, I checked my new site on Websense. I'd installed BlogEngine.NET 2.5 successfully, after figuring out (DOH!) that this new version of BlogEngine required ASP.NET 4.0, instead of the default ASP.NET 2.0 setting that my Web hosting provider uses. Unfortunately, my brand-new site (so new it still has the default BlogEngine content on it) showed up in Websense's scan as Potentially Damaging Content. AARRGGHHH!!!

Ce n'est pas une Integrated Pipeline

It appears that my ASP.NET settings may have been the cause of both of these issues - the Potentially Damaging Content and the missing CSS.

At Arvixe.com (my current hosting company), ASP.NET hosting offers a choice between:

• ASP.NET 1.1
• ASP.NET 2.0
• ASP.NET 2.0 Integrated Pipeline
• ASP.NET 4.0
• ASP.NET 4.0 Integrated Pipeline

I chose the 2.0 Integrated Pipeline setting on this blog, and 4.0 Integrated Pipeline on the new blog. However, I should have chosen the "plain" versions of ASP.NET 2.0 and 4.0 for the old and new versions of my site, according to an article in the Third Party Applications Knowledgebase at Arvixe Support.

I don't know if/when I should use the ASP.NET Integrated Pipeline settings - my Code Monkey evolution hasn't progressed that far yet. But at least now I know not to use it on a BlogEngine.NET site!