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

Restore proxying capability #209

Merged
merged 1 commit into from
Jan 8, 2020
Merged

Conversation

thc202
Copy link
Member

@thc202 thc202 commented Jan 8, 2020

Change ComponentsHttpClient to use a request config with the proxy
settings instead of setting to the context, the latter is ignored when
there's a request config.
Add test to assert that the request is proxied.


Reported in OWASP ZAP User Group: https://groups.google.com/d/topic/zaproxy-users/BzN_pJRiIZM/discussion

Change `ComponentsHttpClient` to use a request config with the proxy
settings instead of setting to the context, the latter is ignored when
there's a request config.
Add test to assert that the request is proxied.

Signed-off-by: thc202 <thc202@gmail.com>
@psiinon psiinon merged commit baad40c into zaproxy:develop Jan 8, 2020
@thc202 thc202 deleted the restore-proxying branch January 8, 2020 14:19
@thc202 thc202 added the bug label Jan 8, 2020
@thc202 thc202 changed the title Restore proyxing capability Restore proxying capability Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

None yet

2 participants