You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When performing pshtt scanning, sometimes we get an error in AWS Lambda stating "other requests response exception". In this case we do not receive scan results for the domain that errored.
To Reproduce
caats3.va.gov is a domain where this happens often.
Expected behavior
A successful scan.
Any helpful log output
None.
The text was updated successfully, but these errors were encountered:
jsf9k
added
the
bug
This issue or pull request addresses broken functionality
label
Jun 20, 2019
@jsf9k I wonder if this has to do with the breaking change in sslyze v2.1.0 in early June where they changed how certificate verification works and so a number of the fields in the certificate plugin went away. I think there were some missing attribute exceptions. See the commits in my fork at echudow@c2f427b and echudow@ce0ccaf for how I addressed this issue with some workarounds to handle both the older and newer versions of sslyze. We're still testing those changes though.
@echudow This issue can't be due to that, since the pshtt lambda hadn't been rebundled since May. Thanks for mentioning that, though, since it will be a problem now (as I'm rebundling to deploy the logging improvements in #197, which will pull in a newer sslyze).
🐛 Bug Report
When performing pshtt scanning, sometimes we get an error in AWS Lambda stating "other requests response exception". In this case we do not receive scan results for the domain that errored.
To Reproduce
caats3.va.gov
is a domain where this happens often.Expected behavior
A successful scan.
Any helpful log output
None.
The text was updated successfully, but these errors were encountered: