I can be that of an ASP.NET MVC form (usually) is a response to "a Submit potentially trigger dangerous request .Form value form the client "to try to get the error around this, I have a ValidateRequest =." showed page directive only problem wrong " :. I'm still getting the error! Now, unless I Aspiknet MVC RC was updated this morning, and (according to Reedme), Visual Web. The following was placed in the config: So, valid should be valid for all the pages, right? Am i missing
In MVC, the verification takes place at the controller level, not at the page level. To see why it is being executed controller's time to take action, we will choose what order to render that do not know it. (Actually, the administrator's action might not render any view! Instead, the file can open the download prompt on the client.) Additionally, if a user is submitting malicious input on the server, the view becomes visible Late in doing anything about this, the controller has already made the database a dangerous input.
Instead, please use the [valid input (wrong)] to decorate the action with the controller or attribute. This will prompt us to suppress the request verification for that controller or verb.
Comments
Post a Comment