Truncate Path, Query and Fragment Endpoint Fields to their Max Column Length #4974
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.
Hi 👋
I noticed that some ZAP reports weren't importing correctly, because the http queries in the endpoints DefectDojo was trying to create were to long for the database schema. I discussed the issue briefly in the slack channel: https://owasp.slack.com/archives/C2P5BA8MN/p1629462343181800
This PR truncates the path, query and fragment attributes to the max length specified in for the database columns.