feat: restrict signed fetch endpoints to only be consumed from explorer client#49
Merged
Merged
Conversation
aleortega
force-pushed
the
feat/restrict-signed-fetch
branch
from
September 30, 2025 20:30
34b6f4e to
4886a90
Compare
Pull Request Test Coverage Report for Build 18142682856Details
💛 - Coveralls |
braianj
approved these changes
Sep 30, 2025
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
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.
This PR updates the endpoints restricted by Signed Fetch so they cannot be consumed from scenes in-world (
metadata.signer !== 'decentraland-kernel-scene').