Hi,
We haven't done a lot of work on DNN is the past few years, but we have a client with a DNN 5.6.1, ASP.NET 4 site we did several years ago. It's a small site, 4 pages, no membership/login capability, just a mom and pop vacuum cleaner business showing what they do. They need a couple of simple changes, an address update on their google map and a HomeAdvisor Award of Excellence image to be displayed on the home page. Pretty simple stuff.
Downloaded the site, restored the database.bak and using VS 2013 Community brought up the site on IIS Express 8.?. The site ran perfectly. We did a login as a superuser and that appeared to work fine. However, whenever we click Edit Content we get the following error:
--------------------------------------------------------------------------------------------------------------------
A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk..."). Description: ASP.NET has detected data in the request that is potentially dangerous because it might include HTML markup or script. The data might represent an attempt to compromise the security of your application, such as a cross-site scripting attack. If this type of input is appropriate in your application, you can include code in a web page to explicitly allow it. For more information, see http://go.microsoft.com/fwlink/?LinkID=212874.
Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk...").
Source Error:
|
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
--------------------------------------------------------------------------------------------------------------------
We get this error regardless of the page or content we're trying to modify. Turns out, we can't change anything without getting this error. When we developed this, we used Visual Web designer 2010/IIS 7.5 and did some maintenance a year ago using 2012. We can go on the actual production site and make changes. Looked up the error and it has to do with checking for cross scripting attacks which shouldn't really manifest itself here, especially since the error doesn't occur on the production site. Could the problem in any way be associated with using VS2013 Community and IIS 8 or a change in SQL Server versions.
Any ideas on what is going on here and how to correct it? Any suggestions would be appreciated.
Cheers,
Larry
|