-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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: close session in case of error to avoid blocked session #11089
fix: close session in case of error to avoid blocked session #11089
Conversation
…session on locking session storage (example unauth_action=deny)
the solution looks good in first observation, let's wait for the CI to run then I will review this again. |
@shreemaan-abhishek Is it possible that ci is flaky? The errors don't seem related to this PR to me. |
@starsz does this feature look good to you? |
t/plugin/openid-connect5.t
Outdated
} | ||
}) | ||
end | ||
ngx.thread.spawn(firstRequest) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can you ensure that the first request is arrived before the second one?
I think maybe you can give a return value of the firstRequest
function , and use ngx.thread.wait
to get the return value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@starsz Thank you for the suggestion, I have implemented a wait for the completion of the first request.
…session on locking session storage (example unauth_action=deny)
Description
This PR is fixing a bug where sessions are blocked until ttl is expired in case of an authentication error. For example unauthenticated session and
unauth_action='deny'
and locking session storage is configured.Basically the same problem as in #10788 but in case of error.
Fixes # (issue)
Checklist