Skip to content
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

Requests parallel processing: #8158

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Keindel
Copy link

@Keindel Keindel commented Nov 1, 2023

This PR is 2nd step to address #8146
Issue needs network addon modification!!! (network thread-sync logic modification) see 1st step PR to zap-extensions zaproxy/zap-extensions#5057

Server-threads in breakpoints: sync, serialization and continue-button logic modified.
Assumptions made are described in comments.

I tried proposed changes - they seem to be working fine. Requests are being processed in parallel, breakpoints wait for user interaction, not blocking other requests.
Probably there are some scenarios requiring further code changes? Please take a look.

- needs network addon modification!!!
- network thread-sync logic modified
- server-threads in breakpoints: sync, serialization and continue-button logic modified

Signed-off-by: Andrey Maksimov <[email protected]>
@thc202
Copy link
Member

thc202 commented Nov 1, 2023

See comment in the referenced zap-extensions PR.

@thc202
Copy link
Member

thc202 commented Nov 1, 2023

Reopening per latest comments in the other PR.

@thc202 thc202 reopened this Nov 1, 2023
@Keindel
Copy link
Author

Keindel commented Jan 16, 2024

Hello!

Its great that 1st PR zaproxy/zap-extensions#5057 regarding the issue #8146 has been merged!

Please consider proposed changes in current PR.
Without these changes in case of having 2 breaks triggered there are still certain problems:

  1. ZAP does not allow further traffic to pass.
  2. After breaking on 1st request and pressing button "Submit and Continue to Next Breakpoint", there is NO breaking 1st response, NO breaking on 2nd request, only breaking on 2nd response. Meanwhile breaking should occur on both requests and both responses.

Proposed in this PR changes solve these problems.

@Keindel
Copy link
Author

Keindel commented Jan 23, 2024

@thc202 @psiinon
please leave some reaction indicating you are aware =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants