Krzysztof Szafrański 731274f39e Fix errors when code, clientId, or tabId are null ... Calling parseSessionCode inside the try-catch would result in ErrorPageException thrown by redirectToErrorPage being caught and re-reported, resulting in one log entry with `invalidRequestMessage` and another one with `unexpectedErrorHandlingRequestMessage`. Additionally, one of ErrorPageException constructors didn't pass the status to super(), resulting in the logger error message being "HTTP 500 Internal Server Error" even though the status was actually something else, like 400. I noticed that ErrorPageException can be simplified by just passing the response to super(), which is one way of fixing the problem. Closes #33232 Signed-off-by: Krzysztof Szafrański <k.p.szafranski@gmail.com>		2024-10-17 14:37:40 -03:00
..
src	Fix errors when code, clientId, or tabId are null	2024-10-17 14:37:40 -03:00
pom.xml	fix: expose bootstrap-admin-* options (#32241)	2024-08-21 15:52:38 +02:00