fix(remix): Don't inject trace/baggage to redirect and catch responses
#8467
Conversation
This file contains 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
AbhiPrasad
approved these changes
Jul 6, 2023
AbhiPrasad
pushed a commit
that referenced
this pull request
Jul 6, 2023
…onses (#8467) Skips `trace` and `baggage` injections to `redirect` and `catch` responses. For `redirect` responses: It was breaking the behaviour of redirection. Internal redirection targets should already have their `trace` and `baggage`, so I assume this should not break the connection between services at the end. `catch` responses do not have bodies, and they are thrown by Remix, so skipping injection as well not to potentially break the internal catch behaviour of Remix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related: epicweb-dev/epic-stack#256
Skips
traceandbaggageinjections toredirectandcatchresponses.For
redirectresponses: It was breaking the behaviour of redirection. Internal redirection targets should already have theirtraceandbaggage, so I assume this should not break the connection between services at the end.catchresponses do not have bodies, and they are thrown by Remix, so skipping injection as well not to potentially break the internal catch behaviour of Remix.