Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix mispelling #187

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix mispelling #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/src/main/asciidoc/servlet-container-profile.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -370,7 +370,7 @@ exception thrown by these methods.

A `ServerAuthModule` must only call `MessageInfo.setResponseMessage()` to wrap or unwrap the existing
response within `MessageInfo`. That is, if a `ServerAuthModule` calls `MessageInfo.setResponseMessage()`,
the response argument must be an `HtppServletResponseWrapper` that wraps the `HttpServletResponse`
the response argument must be an `HttpServletResponseWrapper` that wraps the `HttpServletResponse`
within `MessageInfo`, or the response argument must be an `HttpServletResponse` that is wrapped by the `HttpServletResponseWrapper` within `MessageInfo`. The analogous requirements apply to
`MessageInfo.setRequestMessage()`.

Expand Down Expand Up @@ -530,7 +530,7 @@ the `HttpServletResponse`, but need not do so if the response is unavailable or

The container implementation of `logout` must call `cleanSubject` on the acquired `ServerAuthContext`.
The `MessageInfo` argument to the call to `cleanSubject` must be as defined above. The `clientSubject`
argument must be a non-null `Subject` and should be the `Subject` resulting from the most recent call to `validateRequest` which may have occurred either as described in <<a442>> or as described in <<a487>.
argument must be a non-null `Subject` and should be the `Subject` resulting from the most recent call to `validateRequest` which may have occurred either as described in <<a442>> or as described in <<a487>>.
If the prior `Subject` is not used, a new `clientSubject` must be instantiated and passed in the call.

Following the return from `cleanSubject`, `logout` must perform the logout processing that it performs
Expand Down