Sometimes I really believe that SharePoint actively thwarts my attempts to get it to do what I want. First you look at something and say, wow, that should work. Then you realize it doesn’t. Then you have an epiphany and see a workaround. And when you almost have that work around working… well then SharePoint says no again. Then it’s off on another whirl-wind adventure to find a work around for the workaround. I had one of those issues today, but I think I finally got past the last roadblock.<\/p>\n
So, I was writing an HTTP module as a workaround for another problem. Everything looked like it was working great because I had been slowly adding code into the HTTP module bit by bit in a prototyping effort. Finally I put in the last bit of code in place… and I started to get an error:<\/p>\n
“The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.”<\/strong><\/p>\n This is not an uncommon error – it normally occurs when you are updating an item on a GET request and you have not marked the web containing the item with AllowUnsafeUpdates<\/strong>. One issue, however, is that I wasn’t updating anything in my code. I was, however, getting an SPWeb<\/strong> object so I decided to set the AllowUnsafeUpdates<\/strong> property on it to true<\/strong> for good measure. Once that was in place, I ran it again…<\/p>\n “The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.”<\/strong><\/p>\n