Skip to content
This repository has been archived by the owner on Apr 29, 2022. It is now read-only.

Make HTTP code configurable in http500 rule #80

Open
dividedmind opened this issue Jan 14, 2022 · 4 comments
Open

Make HTTP code configurable in http500 rule #80

dividedmind opened this issue Jan 14, 2022 · 4 comments

Comments

@dividedmind
Copy link
Contributor

BTW, I think maybe it should be changed to flag only 500, or made configurable. While a 500 is almost always a sign of a code problem, other 5xx errors are pretty specific and can be expected (ie. 'not implemented', 'insufficient storage').

Originally posted by @dividedmind in #77 (comment)

@kgilpin
Copy link
Contributor

kgilpin commented Jan 14, 2022 via email

@dividedmind
Copy link
Contributor Author

dividedmind commented Jan 14, 2022

Oh, I hadn't noticed, thanks. Should I leave this issue to make status code configurable though?

EDIT: Actually no, the code still checks for 5xx AFAICT: https://github.com/applandinc/scanner/blob/af2c9fa3e079186c40c8593b97b3d61f236abe42/src/rules/http500.ts

@kgilpin
Copy link
Contributor

kgilpin commented Jan 14, 2022 via email

@dividedmind
Copy link
Contributor Author

I don't think so. Do you think there will be a need to flag other codes?

Some people might want that. There are places where some will be expected, others not. Maybe catch all 500 and allow a whitelist? Not sure what's the best approach here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants