feat(pdp): enforce extraData size limit at the service level #807
+26
−0
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
This PR implements service-level validation for the
extraDatapayload size in PDP (Proof of Data Possession) requests. Following the removal of the hard limit in the PDPVerifier contract (FilOzone/pdp#224), this logic is now enforced within Curio to prevent excessively large metadata payloads from being processed. I have verified these changes locally to ensure that the limits are enforced correctly and oversized payloads are rejected.Fixes #713
Changes Proposed
1. Defined Size Limits
MaxCreateDataSetExtraDataSize: Set to 4KB (4096 bytes) forcreateDataSet.MaxAddPiecesExtraDataSize: Set to 8KB (8192 bytes) foraddPiecesandcreateDataSetAndAddPieces.2. Validation Logic (Fail Fast)
Implemented size checks in the following handlers:
handleCreateDataSethandleCreateDataSetAndAddPieceshandleAddPieceToDataSetChecklist