diff --git a/securing_apps/topics/oidc/java/adapter_error_handling.adoc b/securing_apps/topics/oidc/java/adapter_error_handling.adoc index 594384b322..969e5897a2 100644 --- a/securing_apps/topics/oidc/java/adapter_error_handling.adoc +++ b/securing_apps/topics/oidc/java/adapter_error_handling.adoc @@ -5,12 +5,12 @@ {{book.project.name}} has some error handling facilities for servlet based client adapters. When an error is encountered in authentication, {{book.project.name}} will call `HttpServletResponse.sendError()`. You can set up an error-page within your `web.xml` file to handle the error however you want. -{{book.project.name}} may throw 400, 401, 403, and 500 errors. +{{book.project.name}} can throw 400, 401, 403, and 500 errors. [source,xml] ---- - 404 + 403 /ErrorHandler ---- diff --git a/securing_apps/topics/saml/java/error_handling.adoc b/securing_apps/topics/saml/java/error_handling.adoc index 3929ae9936..f271adc8db 100644 --- a/securing_apps/topics/saml/java/error_handling.adoc +++ b/securing_apps/topics/saml/java/error_handling.adoc @@ -4,13 +4,13 @@ {{book.project.name}} has some error handling facilities for servlet based client adapters. When an error is encountered in authentication, the client adapter will call `HttpServletResponse.sendError()`. You can set up an `error-page` within your `web.xml` file to handle the error however you want. -The client adapter may throw 400, 401, 403, and 500 errors. +The client adapter can throw 400, 401, 403, and 500 errors. [source,xml] ---- - 404 + 403 /ErrorHandler ----