feat(security): add 'empty' to forbidden fetch destinations #317
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.
Checklist
Description
This PR adds 'empty' to the list of forbidden fetch destinations in the
do_process_payloadfunction. This change prevents the processing of requests that have an empty fetch destination, which could potentially be used for malicious purposes or cause unnecessary processing overhead.Changes
fastly-edgee/src/proxy/compute/mod.rsSecurity Impact
This change improves security by preventing potential abuse through empty fetch destinations.
Related Issues
List related issues here