I have been working with a local copy of DNN 5.6.0 on a customers site. When accessing a standard page from DNN, to change a users password, redirected from the profile page, the following message has been appearing and had to be implemented in order to continue working. It would seem that the core code should be modified rather than implement this modification. Could someone please verify?

A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk...").

Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. To allow pages to override application request validation settings, set the requestValidationMode attribute in the httpRuntime configuration section to requestValidationMode="2.0". Example: <httpRuntime requestValidationMode="2.0" />. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the <pages> configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case. For more information, see http://go.microsoft.com/fwlink/?LinkI....

Thanx

---

Thanx

L Douglas

 Hello, I was reading through the forum in search for a solution to my problem (dangerousn Request.QueryString error pops up whenever I try to change the portal skin)
I realised that I can run my freshly upgraded 5.6 DNN installation without errors ONLY if I set validateRequest="false" in the pages section. Plus I tried adding requestValidationMode="2.0" to my httpRuntime section in web config and it does work and solve the problem (only if I set validation to False) but a red squiggly line appears under it...

Any ideas as to how I could solve these problems before I try to upgrade my live version from 4.9.5 to 5.6 via 5.4.4...?

Thank you