Sanitize/validate input in ASP.NET 5 and MVC 6
Per this page, in ASP.NET 5, you cannot depend on request validation, which I believe was a feature of IIS/ASP.NET. Since ASP.NET 5 can be self-hosted with linux support, we must do it our selves. Sounds good.
The question is, what is the recommend way to do it for ASP.NET 5? Is there a built in MVC 6 attribute that will sanitize/validate? What exactly did the old way detect? Script tags? Style tags?
asp.net-core asp.net-core-mvc sanitization
add a comment |
Per this page, in ASP.NET 5, you cannot depend on request validation, which I believe was a feature of IIS/ASP.NET. Since ASP.NET 5 can be self-hosted with linux support, we must do it our selves. Sounds good.
The question is, what is the recommend way to do it for ASP.NET 5? Is there a built in MVC 6 attribute that will sanitize/validate? What exactly did the old way detect? Script tags? Style tags?
asp.net-core asp.net-core-mvc sanitization
Regarding the article no difference for asp.net 5. Just use viewmodels with display annotations for the properties.
– devfric
Dec 26 '15 at 7:11
Before asp.net 5, the request framework itself (httpmodules/handlers) had request validation built in. You could disable it via the web.config, but it was a feature of the handlers in the GAC, used in IIS. I am aware of how to do this myself using model attributes, but so far, there is no official way to do this from Microsoft, and their should be. Perhaps a middleware that intercepts posted form values for site-wide usage by default? Idk. This is very important in web development, and an answer should be provided by Microsoft on how we should do it.
– Paul Knopf
Dec 29 '15 at 20:27
add a comment |
Per this page, in ASP.NET 5, you cannot depend on request validation, which I believe was a feature of IIS/ASP.NET. Since ASP.NET 5 can be self-hosted with linux support, we must do it our selves. Sounds good.
The question is, what is the recommend way to do it for ASP.NET 5? Is there a built in MVC 6 attribute that will sanitize/validate? What exactly did the old way detect? Script tags? Style tags?
asp.net-core asp.net-core-mvc sanitization
Per this page, in ASP.NET 5, you cannot depend on request validation, which I believe was a feature of IIS/ASP.NET. Since ASP.NET 5 can be self-hosted with linux support, we must do it our selves. Sounds good.
The question is, what is the recommend way to do it for ASP.NET 5? Is there a built in MVC 6 attribute that will sanitize/validate? What exactly did the old way detect? Script tags? Style tags?
asp.net-core asp.net-core-mvc sanitization
asp.net-core asp.net-core-mvc sanitization
asked Dec 25 '15 at 6:56
Paul KnopfPaul Knopf
4,1011754113
4,1011754113
Regarding the article no difference for asp.net 5. Just use viewmodels with display annotations for the properties.
– devfric
Dec 26 '15 at 7:11
Before asp.net 5, the request framework itself (httpmodules/handlers) had request validation built in. You could disable it via the web.config, but it was a feature of the handlers in the GAC, used in IIS. I am aware of how to do this myself using model attributes, but so far, there is no official way to do this from Microsoft, and their should be. Perhaps a middleware that intercepts posted form values for site-wide usage by default? Idk. This is very important in web development, and an answer should be provided by Microsoft on how we should do it.
– Paul Knopf
Dec 29 '15 at 20:27
add a comment |
Regarding the article no difference for asp.net 5. Just use viewmodels with display annotations for the properties.
– devfric
Dec 26 '15 at 7:11
Before asp.net 5, the request framework itself (httpmodules/handlers) had request validation built in. You could disable it via the web.config, but it was a feature of the handlers in the GAC, used in IIS. I am aware of how to do this myself using model attributes, but so far, there is no official way to do this from Microsoft, and their should be. Perhaps a middleware that intercepts posted form values for site-wide usage by default? Idk. This is very important in web development, and an answer should be provided by Microsoft on how we should do it.
– Paul Knopf
Dec 29 '15 at 20:27
Regarding the article no difference for asp.net 5. Just use viewmodels with display annotations for the properties.
– devfric
Dec 26 '15 at 7:11
Regarding the article no difference for asp.net 5. Just use viewmodels with display annotations for the properties.
– devfric
Dec 26 '15 at 7:11
Before asp.net 5, the request framework itself (httpmodules/handlers) had request validation built in. You could disable it via the web.config, but it was a feature of the handlers in the GAC, used in IIS. I am aware of how to do this myself using model attributes, but so far, there is no official way to do this from Microsoft, and their should be. Perhaps a middleware that intercepts posted form values for site-wide usage by default? Idk. This is very important in web development, and an answer should be provided by Microsoft on how we should do it.
– Paul Knopf
Dec 29 '15 at 20:27
Before asp.net 5, the request framework itself (httpmodules/handlers) had request validation built in. You could disable it via the web.config, but it was a feature of the handlers in the GAC, used in IIS. I am aware of how to do this myself using model attributes, but so far, there is no official way to do this from Microsoft, and their should be. Perhaps a middleware that intercepts posted form values for site-wide usage by default? Idk. This is very important in web development, and an answer should be provided by Microsoft on how we should do it.
– Paul Knopf
Dec 29 '15 at 20:27
add a comment |
1 Answer
1
active
oldest
votes
I recommend FluentValidation for ASP.NET 5:
public class PersonValidator : AbstractValidator<Person> {
public PersonValidator() {
RuleFor(x => x.Id).NotNull();
RuleFor(x => x.Name).Length(0, 10);
RuleFor(x => x.Email).EmailAddress();
RuleFor(x => x.Age).InclusiveBetween(18, 60);
}
}
https://fluentvalidation.net/aspnet#asp-net-mvc-5
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f34460724%2fsanitize-validate-input-in-asp-net-5-and-mvc-6%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I recommend FluentValidation for ASP.NET 5:
public class PersonValidator : AbstractValidator<Person> {
public PersonValidator() {
RuleFor(x => x.Id).NotNull();
RuleFor(x => x.Name).Length(0, 10);
RuleFor(x => x.Email).EmailAddress();
RuleFor(x => x.Age).InclusiveBetween(18, 60);
}
}
https://fluentvalidation.net/aspnet#asp-net-mvc-5
add a comment |
I recommend FluentValidation for ASP.NET 5:
public class PersonValidator : AbstractValidator<Person> {
public PersonValidator() {
RuleFor(x => x.Id).NotNull();
RuleFor(x => x.Name).Length(0, 10);
RuleFor(x => x.Email).EmailAddress();
RuleFor(x => x.Age).InclusiveBetween(18, 60);
}
}
https://fluentvalidation.net/aspnet#asp-net-mvc-5
add a comment |
I recommend FluentValidation for ASP.NET 5:
public class PersonValidator : AbstractValidator<Person> {
public PersonValidator() {
RuleFor(x => x.Id).NotNull();
RuleFor(x => x.Name).Length(0, 10);
RuleFor(x => x.Email).EmailAddress();
RuleFor(x => x.Age).InclusiveBetween(18, 60);
}
}
https://fluentvalidation.net/aspnet#asp-net-mvc-5
I recommend FluentValidation for ASP.NET 5:
public class PersonValidator : AbstractValidator<Person> {
public PersonValidator() {
RuleFor(x => x.Id).NotNull();
RuleFor(x => x.Name).Length(0, 10);
RuleFor(x => x.Email).EmailAddress();
RuleFor(x => x.Age).InclusiveBetween(18, 60);
}
}
https://fluentvalidation.net/aspnet#asp-net-mvc-5
answered Nov 20 '18 at 12:19
RebeccaRebecca
9,7101068111
9,7101068111
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f34460724%2fsanitize-validate-input-in-asp-net-5-and-mvc-6%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Regarding the article no difference for asp.net 5. Just use viewmodels with display annotations for the properties.
– devfric
Dec 26 '15 at 7:11
Before asp.net 5, the request framework itself (httpmodules/handlers) had request validation built in. You could disable it via the web.config, but it was a feature of the handlers in the GAC, used in IIS. I am aware of how to do this myself using model attributes, but so far, there is no official way to do this from Microsoft, and their should be. Perhaps a middleware that intercepts posted form values for site-wide usage by default? Idk. This is very important in web development, and an answer should be provided by Microsoft on how we should do it.
– Paul Knopf
Dec 29 '15 at 20:27