aspnetcore/test/WebSites
Patrick Westerhoff ddbe0fef26 Allow custom handling of antiforgery failures
To enable custom handling of antiforgery validation failures, use an
`AntiforgeryValidationFailedResult` which is just a `BadRequestResult`
but allows to be identified explicitly inside always-running result
filters using the `IAntiforgeryValidationFailedResult` marker interface.
2018-10-19 13:47:08 -07:00
..
ApiExplorerWebSite
ApplicationModelWebSite
BasicWebSite Allow custom handling of antiforgery failures 2018-10-19 13:47:08 -07:00
Common Support page parameter in attribute route (#8530) 2018-10-04 14:39:40 +13:00
ControllersFromServicesClassLibrary
ControllersFromServicesWebSite
CorsWebSite
ErrorPageMiddlewareWebSite
FSharpWebSite
FilesWebSite
FormatterWebSite Shortcircuit validation when using default validator providers and no validation metadata is discovered 2018-10-12 14:47:06 -07:00
HtmlGenerationWebSite
RazorBuildWebSite
RazorBuildWebSite.PrecompiledViews
RazorBuildWebSite.Views
RazorPagesClassLibrary
RazorPagesWebSite Handle OPTIONS requests without a handler in Razor Pages (#8528) 2018-10-04 12:25:36 -07:00
RazorWebSite
RoutingWebSite Fix PageRouteTransformerConvention with custom page routes (#8576) 2018-10-10 18:33:30 +13:00
SecurityWebSite
SimpleWebSite
TagHelpersWebSite
VersioningWebSite Support page parameter in attribute route (#8530) 2018-10-04 14:39:40 +13:00
WebApiCompatShimWebSite
XmlFormattersWebSite Use compat flag to drive XML ProblemDetails formatting 2018-10-12 14:15:28 -07:00
Directory.Build.props