ref(forward): Never forward in processing Relays#5915
Open
Conversation
Dav1dde
force-pushed
the
dav1d/never-forward-in-processing
branch
from
ef018f9 to
df66dfc
Compare
jjbayer
approved these changes
Apr 30, 2026
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
2 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.
There is never a need to forward requests through to Sentry anymore.
This used to be useful where certain endpoints were only implemented by Sentry and not Relay. Now since Relay explicitly implements the register and challenge endpoints, there is no need for this anymore.
Refs: INGEST-887 - an adjacent fix for self hosted.