Feature request: running second order with auth cookie header ?

Question

Feature request: running second order with auth cookie header ?

ehsandeep opened this issue 7 years ago · 8 comments

ehsandeep commented 7 years ago

in this way it may can explore more files, i mean -js files maybe ?

ehsandeep commented 7 years ago

Thanks.

Answer 1 · 2017-07-22T21:47:20.000Z

Good idea. It's on my ToDo list. I'll probably add it soon. Thanks!

Answer 2 · 2017-09-04T11:54:42.000Z

Hi,

Just pushed the update. Now, you can use the -cookie flag to supply a list of comma-delimited cookies.

Thanks

Answer 3 · 2017-09-04T14:19:04.000Z

Great work @mhmdiaa, just curious if it supports Header as well? nowadays web applications use header based authentication as well.

Answer 4 · 2017-09-04T15:33:51.000Z

Thanks. Right now, it doesn't, but it's on the backlog along with some other updates. BTW, if you know Go, pull requests are very welcome :)

Answer 5 · 2017-09-06T10:15:56.000Z

Sure, 1 more thing to notice @mhmdiaa, blacklist given endpoints to stop crawler to get logged out from application.

Answer 6 · 2017-09-10T18:10:17.000Z

Hey @mhmdiaa, is blacklist approach is for listed domain names only or it support the path as well eg: domain.com/logout ?

Answer 7 · 2017-09-10T21:12:24.000Z

Hi @MadaraTech, yes domain.com/logout would work perfectly. The blacklist is basically a list of regular expressions that will be matched against the found URLs.

P.S: Pull the latest update. Due to a bug on the code, URLs were checked if they were found by a query, but not if they were scheduled to be crawled. I just fixed that.