Closed jwoertink closed 1 year ago
@jwoertink I ran the whole spec suite now, and didn't see an issue. I don't think there is some inherent issue.. I do know that dom_xss is for now disabled but I don't think this should have caused the Socket connection issue....
@derevnjuk any ideas?
@jwoertink does it fail only on the head
version of Crystal?
oh, do I need to remove dom_xss
? Also, this is on latest, not head
. So 1.10.1.
Just re-ran the spec and I got an email
Unfortunately, a problem occurred with scan Please check the scan engine logs or contact support. Error: The repeater has not been responding for 10 minutes. The scan has been disrupted.
Ran again, and it all passed... Could have been a fluke? Maybe the CI was having a Monday? :man_shrugging: I won't worry too much about it for now, but let me know about the dom_xss
if I should remove it, and what other tests I might have to remove from default.
@jwoertink you can use xss instead of dom_xss.
We found an issue with scans longer then 10 minutes, I'm looking into it, we need to add a ping to our servers otherwise we decide the repeater is down.
@derevnjuk noticed this behavior
Fixed via: ecb8f52fd98f80986b51ae624d6432835c880f0e
When I run this spec in Lucky, I'm getting a "Closed socket" error
This is running on the latest release, but maybe I'm missing a setup somewhere since the repeater moved to Crystal?