Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Hey guys, there's a bug when processing offsite on a custom port #17
So you are starting on a custom port and when it tries to check another site it reverts to port 80 and fails, is that the problem?…
On Fri, 28 Apr 2017 at 16:21 danilo ***@***.***> wrote: [image: selection_739] <https://cloud.githubusercontent.com/assets/2204686/25535306/f5e51bc4-2c0c-11e7-979f-ab7648e53e17.png> ..it falls back to port 80. thx. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#17>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHJWXy-8cBvfaSoA0eZNwuzdiWSWwNJks5r0gPvgaJpZM4NLoDH> .
it reverts to 80..
..but is the same site!
If I start cewl without -o flag, it does not even spider those urls..
Anyway, solved the problem on iptables forwarding localhost:80 to remotesite:32914
Are you using the latest from github? Thought I'd tested all this when I added the last port checking…
On Fri, 28 Apr 2017, 17:44 danilo, ***@***.***> wrote: Same site.. I start from http://website.com:32914 But when it starts getting the internal urls like: http://website.com:32914/hello-world http://website.com:32914/hello-world2 it reverts to 80, but is the same site! If I start cewl without -o flag, it does not even spider those urls.. By the way, solved the problem on iptables forwarding remotesite:32914 to localhost:80.. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHJWQIKzI6zxQPVmSh7iC8j5564p3yKks5r0hdWgaJpZM4NLoDH> .