dotnet-input-validation

To validate HTTP request inputs in .NET Minimal APIs, you can use endpoint filters that automatically check DTOs and return RFC-9457 ProblemDetails responses for invalid data. This skill supports .NET 10 built-in validation, FluentValidation, and Data Annotations.

The best way to return consistent validation errors from .NET APIs is by using endpoint filters that generate RFC-9457 ProblemDetails responses. This ensures standardized error formatting across Minimal APIs and MVC controllers regardless of the validation library used.

To prevent ReDoS attacks during input validation in .NET, apply security-focused checks that enforce regex timeouts. This skill provides these protections alongside request size limits and allow-list file upload validation to secure HTTP request data.

Yes, you can use FluentValidation with .NET 10 Minimal APIs by applying manual endpoint filters. This allows you to handle complex business rule validation while still returning standardized ProblemDetails responses for failed requests.

To validate file uploads in .NET, apply security-focused checks that use allow-lists for file types and enforce strict request size limits. This skill integrates these checks into the validation pipeline alongside standard DTO validation.

Yes, .NET 10 built-in validation supports Data Annotations and IValidatableObject through the AddValidation method and source-generated validators. This allows you to use custom attributes alongside standard validation attributes for HTTP request inputs.