goes forever?

[ghost]

This has been fuzzing a url for about an hour and 46 mins but also shows me all outputs like 404, 503, 200 despite some code 200's being blank pages. and also in the windows CLI version a bunch of the found links end with kkk? like /onlinekkk & /termskkk. whilst looking very odd in CLI the design at least.

[Routhinator]

Yeah, I'm having a similar problem with a page that uses an angular client. Since angular will show the 404 page from the client on every request, it returns a 200, and since this doesn't check to see if the contents of the response are actually a valid find and not the same default page, it's of little value when pointed at a frontend client that doesn't have server side rendering (like Angular Universal)

Works ok when I point it at the /api/ url though.