Closed chrishaensel closed 1 year ago
This appears to be not due to http
, but rather because the page has long lived network requests that don't complete. Currently Horseman relies on networkidle0
, which never happens with that site.
The solution will be for me to add settings to allow you to specify the desired waitUntil
options.
Fixed in 0.2.0 by allowing the user to pick the waituntil option.
For me, horseman isn't crawling when using a HTTP URL (not https) as a start URL. Sample URL: http://www.insecam.org