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

Do not report 403 (Forbidden) status as an error #9

Open
mthuurne opened this issue Feb 21, 2019 · 0 comments
Open

Do not report 403 (Forbidden) status as an error #9

mthuurne opened this issue Feb 21, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@mthuurne
Copy link
Member

mthuurne commented Feb 21, 2019

HTTP status code 403 (Forbidden) is in the client errors (4xx) range. However, there are valid reasons for a site under test to return a 403 status, so reporting it as an error would be a false positive.

How should it be reported though? There is a risk that the test was misconfigured and the 403 is preventing parts of the site from being tested; counting requests resulting in 403 as passed would hide such problems. So it might be worth adding a separate category for this that is neither passed nor failed.

Another question is whether to check the document body by default. I think this would depend on whether the error page is generated by the software under test or by a web server in front of it. See issue #7.

@mthuurne mthuurne added the bug Something isn't working label Feb 21, 2019
@mthuurne mthuurne changed the title Do not report 403 (Forbidden) status an error Do not report 403 (Forbidden) status as an error May 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant