Take into account multiple Set-Cookie headers in logDebugResponseCookie #326
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While investigating a lost session on login issue, I came across this issue in trace level debugging. Our app which uses Apache Shiro is currently sending out two Set-Cookie headers, one for deleting a remember me cookie and one for setting the JSESSIONID. The current code doesn't always emit a log entry in logDebugResponseCookie presumably because which of these headers is actually processed is non-deterministic. This small patch will go through all Set-Cookie headers and emit a log entry for each session cookie.