curiouswebster
asked on
A potentially dangerous Request.Path value was detected from the client (?).
I have an MVC3 web application and a second Dynamic Data website used for data administration. I want a link from the MVC3 to the Dynamic Data site, and have created the code which will redirect it. At the moment it looks like this,
string url = http://localhost:4189/WebAdmin/%3Fun3Dmyusername%3D353494271.949838
since in development I have hard coded the path "http://localhost:4189/WebAdmin/%" into my web config. The problem is that when I call Response.Redirect(url) I get the YellowScreenOfDeath with the above error (in subject).
Should I use somethign besides Response.Redirect()?
Thanks,
newbieweb
string url = http://localhost:4189/WebAdmin/%3Fun3Dmyusername%3D353494271.949838
since in development I have hard coded the path "http://localhost:4189/WebAdmin/%" into my web config. The problem is that when I call Response.Redirect(url) I get the YellowScreenOfDeath with the above error (in subject).
Should I use somethign besides Response.Redirect()?
Thanks,
newbieweb
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
<pages> is highlighted...
Line 112: </providers>
Line 113: </roleManager>
Line 114: <pages>
Line 115: <namespaces>
Line 116: <add namespace="System.Web.Mvc" />
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
<pages> is highlighted...
Line 112: </providers>
Line 113: </roleManager>
Line 114: <pages>
Line 115: <namespaces>
Line 116: <add namespace="System.Web.Mvc"
ASKER
I think I mis-understood. I need to update the target web.config. I am testing that now...
ASKER
That worked!
where you are redirecting