Repository navigation
enh: rework form resubmit via self-dispatch rather than a network-call - #2900
Conversation
|
For now, this is full of AI slop, but it (at least tests pass) works?. Needs lots of refactoring and simplification, so the code actually makes some sense |
…sting/jakarta/ee/servlets/ExceptionServlet.java
ff97a29 to
78782a3
Compare
|
Got rid of lots of AI slop for now, time for real review and manual refactoring. |
|
Ran in production for a few days, no regressions found, functionality works in real applications. |
| } | ||
| response.addCookie(cookieToDelete); | ||
| @NonNull String cookieName, boolean useHostPrefix) { | ||
| response.addCookie(newCookie(servletContext, cookieName, "tbd", 0, useHostPrefix)); |
There was a problem hiding this comment.
Some warnings here... not sure if they are valid or already taken care of...?
There was a problem hiding this comment.
I dont see any warnings, can you paste them in? Where are you getting the warnings?
| /** | ||
| * Replayed responses are captured and only applied to the browser on demand | ||
| */ | ||
| @ExtendWith(MockitoExtension.class) |
There was a problem hiding this comment.
👍 For tests of new classes
|
>>>> Lenny Primak ***@***.***>:
I dont see any warnings, can you paste them in? Where are you getting the warnings?
The warnings were in the PR close to where I made the comment.
|
|
Are you talking about GH advanced security / CodeQL warnings? They are all dismissed as false positives because they are :) |
|
>>>> Lenny Primak ***@***.***>:
lprimak left a comment (apache/shiro#2900)
Are you talking about GH advanced security / CodeQL warnings? They are all dismissed as false positives because they are :)
Ah, ok!
I will approve the PR then.
|
Internals of data loss prevention / data save functionality is redone without a network call.
Ran security model tests with LLMs, with only improvements reported (no regressions)
TODO: update docs on the website.This has been done.Following this checklist to help us incorporate your contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a GitHub issue. Your pull request should address just this issue, without pulling in other changes.
[#XXX] - Fixes bug in SessionManager,where you replace
#XXXwith the appropriate GitHub issue. Best practiceis to use the GitHub issue title in the pull request title and in the first line of the commit message.
fixes #XXXif merging the PR should close a related issue.mvn verifyto make sure basic checks pass. A more thorough check will be performed on your pull request automatically.Trivial changes like typos do not require a GitHub issue (javadoc, comments...).
In this case, just format the pull request title like
[DOC] - Add javadoc in SessionManager.If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.