Address potential classloader performance issues in JS scripts#504
Address potential classloader performance issues in JS scripts#504kingthorin wants to merge 1 commit intozaproxy:mainfrom
Conversation
|
Note I used |
|
New Issues (5)Checkmarx found the following issues in this Pull Request
Fixed Issues (2)Great job! The following issues were fixed in this Pull Request
Use @Checkmarx to reach out to us for assistance. Just send a PR comment with Examples: |
39d4e87 to
80916f9
Compare
|
The CX failure is unrelated to the changes. |
passive/Report non static sites.js
Outdated
| @@ -73,7 +76,5 @@ function appliesToHistoryType(historyType) { | |||
| // return historyType == org.parosproxy.paros.model.HistoryReference.TYPE_SPIDER; | |||
There was a problem hiding this comment.
I was suggesting doing the same as the other cases move it to the script declaration not keep it inside the function.
There was a problem hiding this comment.
At HistoryReference or SPIDER_TYPE?
Signed-off-by: kingthorin <[email protected]>
80916f9 to
f6c4ce7
Compare
|
Think I got all those. |
| - Active and passive READMEs to include lastest JS script examples. | ||
| - Reduce usage of fully qualified objects in loops or main methods to address potential classloader performance issues, in JavaScript scripts (Issue 9187). | ||
| - Updated Alert_on_HTTP_Response_Code_Errors.js to work with GraalVM JavaScript engine. | ||
|
|
|
Not all scripts were updated (some still left in the changed scripts), was that on purpose? |
|
I thought I copied the full content from zaproxy/docker will check. |
|
I'm referring to scripts that are just here (e.g. |
|
My search must have missed them, thanks for clarifying. |
|
I just remembered there were a few I left on purpose like in the extender scripts cause they're only used on install and uninstall or register and unregister, but I guess I should change them all to be consistent. |



No description provided.