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
HPCC-20557 Return special error for wrong esp session request #11721
Conversation
https://track.hpccsystems.com/browse/HPCC-20557 |
@RussWhitehead please review. |
{ | ||
if (strieq(method, "lock") || strieq(method, "unlock")) | ||
{ | ||
VStringBuffer errMsg("Action not support: %s", method); |
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.
Is this displayed to a user? If so it should read "Action not supported:"
@RussWhitehead Please review my changes. |
@wangkx Looks good |
If a session enabled ESP was used and some web page is still open, the session timer may trig a session lock request to ESP even if the ESP has been switched to a session disabled ESP. In this fix, ESP will detect the problem and return an 'Action not supported:...' error to the session timer. Also clear session cookies from ESP side. Signed-off-by: wangkx <kevin.wang@lexisnexis.com>
Automated Smoketest: ✅ Unit tests result:
Regression test result:
HPCC Stop: OK
|
@richardkchapman this PR is ready to be merged. |
If a session enabled ESP was used and some web page is still open,
the session timer may trig a session lock request to ESP even if
the ESP has been switched to a session disabled ESP. In this fix,
ESP will detect the problem and return an 'Action not support:...'
error to the session timer. Also clear session cookies from ESP
side.
Signed-off-by: wangkx kevin.wang@lexisnexis.com
Type of change:
Checklist:
Testing: