daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add comma (#4894)

pull/4895/head
Michael DePouw 2017-11-29 17:01:14 -05:00 committed by Rick Anderson
parent 604f717e29
commit 4b11174d8c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/security/authorization/policies.md
View File

@ -144,7 +144,7 @@ You can see in our [handler example](policies.md#security-authorization-handler-
* To guarantee failure even if other handlers for a requirement succeed, call `context.Fail`.
Regardless of what you call inside your handler all handlers for a requirement will be called when a policy requires the requirement. This allows requirements to have side effects, such as logging, which will always take place even if `context.Fail()` has been called in another handler.
Regardless of what you call inside your handler, all handlers for a requirement will be called when a policy requires the requirement. This allows requirements to have side effects, such as logging, which will always take place even if `context.Fail()` has been called in another handler.
<a name="security-authorization-policies-based-multiple-handlers"></a>