Adding Content-Type to all output formats (#336) #341
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I think it's a good feature. Though I'd like to keep consistent throughout the different output file type options. Do you think it could be feasible to add these to the HTML and MD output formats as well? |
Contributor
Author
|
Done, it is for sure better to keep consistency between all output formats. |
Contributor
|
Hey guys, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The JSON and CSV output file formats now include the
Content-Typein the output. I think this is useful for everyone that is using ffuf to automate their recon and can now use the content-type to determine if a specific endpoint may be interesting or not.Fixes: #336
Additonally
CONTRIBUTORS.md.The file should be alphabetically ordered.
CHANGELOG.md