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

fix missing exception handling #5019

Merged

Conversation

thelightcosine
Copy link

a few of our http login scanners needed to handle a couple of other exception classes for when network communication errors occur.

There's not really a lot of manual verification that can happen here as it is highly situational.

MSP-12389

a few of our http login scanners needed to
handle a couple of other exception classes
for when network communication errors occur

MSP-12389
@thelightcosine thelightcosine added bug jira Old label, generally associated with PRs that had pro support and a jira link labels Mar 27, 2015
@wchen-r7 wchen-r7 self-assigned this Mar 28, 2015
@thelightcosine
Copy link
Author

D'oh !

accidentally dropped Errno::ETIMEDOUT from the exception
handling

MSP-12389
@Meatballs1
Copy link
Contributor

Could these be declared as some kind of constant or summat? :D

@jlee-r7
Copy link
Contributor

jlee-r7 commented Mar 30, 2015

IMO, Errno::ECONNRESET should instead be SystemCallError, which covers all the Errnos.

@hdm
Copy link
Contributor

hdm commented Mar 30, 2015

Most of them are rolled up into a Rex exception as well (like ConnectionError). Maybe updating the rollup classes and exception handling would be better?

@todb-r7
Copy link

todb-r7 commented Mar 30, 2015

Landing this now so it can hit the next release cut. No verification steps makes me sad, but now that it's merely adding some extra classes to the rescue, I'm not worried about it.

@todb-r7 todb-r7 merged commit 103373a into rapid7:master Mar 30, 2015
todb-r7 pushed a commit that referenced this pull request Mar 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug jira Old label, generally associated with PRs that had pro support and a jira link library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants