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.

Sign up for GitHub

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

Jump to bottom

go client API does not return error when http response status code is >= 400 #1

Closed

oberg-s opened this issue Dec 7, 2020 · 0 comments · May be fixed by zaproxy/zap-api-go#11

Assignees

oberg-s commented Dec 7, 2020 •

edited

Loading

e.g. The error return parameter is almost always nil unless there is an underlying transport error.

Dec 04 17:27:07 xxx-portal.deepfactor.io webappsvc[50652]: time="2020-12-04T17:27:07Z" level=info msg="WebAppScan zap Active scan userID: , r: map[code:url_not_found message:URL Not Found in the Scan Tree], err: <nil>"

The text was updated successfully, but these errors were encountered:

oberg-s self-assigned this

oberg-s added a commit that referenced this issue


          Add error to client API when http status >= 400

f1f4c51

Fixes #1

oberg-s mentioned this issue

Add error to client API when http status >= 400 zaproxy/zap-api-go#11

Open

oberg-s added a commit that referenced this issue


          Add error to client API when http status >= 400

9bc50fe

Fixes #1

Signed-off-by: Scott Oberg <[email protected]>

oberg-s added a commit that referenced this issue


          Add error to client API when http status >= 400

e673c8b

Fixes #1

Signed-off-by: Scott Oberg <[email protected]>

rizwanmerchant closed this as completed

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