Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include url response body in the callback function OnResult. #360

Closed
fetlife1 opened this issue Mar 16, 2023 · 1 comment · Fixed by #312
Closed

Include url response body in the callback function OnResult. #360

fetlife1 opened this issue Mar 16, 2023 · 1 comment · Fixed by #312
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.
Milestone

Comments

@fetlife1
Copy link

Would be nice to have http response body in the callback response, for example as a ReponseBody field in the Result struct

 OnResult: func(result output.Result) { // Callback function to execute for result 
      fmt.Printf("respone body is %s\n",result.ResponseBody)    
    },    
  } 

Use case: Useful for scanning the website's html code without having to the request the same url again for example looking for secrets or running a regex across all found endpoitns, saving time and resources for the developer, and http response is probably laying around in some variable, might as well make use of it :)

@fetlife1 fetlife1 added the Type: Enhancement Most issues will probably ask for additions or changes. label Mar 16, 2023
@ehsandeep
Copy link
Member

@fetlife1 this will be possible with #312

@Mzack9999 Mzack9999 linked a pull request Mar 17, 2023 that will close this issue
@Mzack9999 Mzack9999 self-assigned this Mar 17, 2023
@Mzack9999 Mzack9999 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Mar 17, 2023
@ehsandeep ehsandeep added this to the katana v.1.0.0 milestone Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants