A potentially dangerous Request.QueryString value was detected from the client (ReturnUrl="...1111&#Write"). [modified]
-
i would like my application redirect after login. Url: http://mySite.com/Login.aspx?ReturnUrl=http%3A%2F%2FmySite.com%2Fpage.aspx%3F%26pid%3D1111%26%23Write But don't know why the application return a error: A potentially dangerous Request.QueryString value was detected from the client (ReturnUrl="...1111&#Write"). Could anyone help?
modified on Thursday, October 9, 2008 5:12 AM
-
i would like my application redirect after login. Url: http://mySite.com/Login.aspx?ReturnUrl=http%3A%2F%2FmySite.com%2Fpage.aspx%3F%26pid%3D1111%26%23Write But don't know why the application return a error: A potentially dangerous Request.QueryString value was detected from the client (ReturnUrl="...1111&#Write"). Could anyone help?
modified on Thursday, October 9, 2008 5:12 AM
I think that it's the http:// part of the data that it reacts on. Try to use a relative url instead of a fully qualified url. Otherwise you can turn of ValidateRequest in the @Page directive.
Despite everything, the person most likely to be fooling you next is yourself.
-
i would like my application redirect after login. Url: http://mySite.com/Login.aspx?ReturnUrl=http%3A%2F%2FmySite.com%2Fpage.aspx%3F%26pid%3D1111%26%23Write But don't know why the application return a error: A potentially dangerous Request.QueryString value was detected from the client (ReturnUrl="...1111&#Write"). Could anyone help?
modified on Thursday, October 9, 2008 5:12 AM
Because some idiot thought it would be fun to make ASP.Net websites crash randomly. This ill-designed "protection" is causing more harm than good in each and every website where it's not turned off. And now it seems in ASP.Net MVC 2 it can't be turned off. I've already modified web.config and this idiotic message still appears. Hey dude, I ain't ever gonna include that value unescaped in the HTML, shut the heck up!