Skip to content

fix(remix): Don't inject trace/baggage to redirect and catch responses#8467

Merged
AbhiPrasad merged 1 commit intodevelopfrom
onur/fix-remix-redirect-responses
Jul 6, 2023
Merged

fix(remix): Don't inject trace/baggage to redirect and catch responses#8467
AbhiPrasad merged 1 commit intodevelopfrom
onur/fix-remix-redirect-responses

Conversation

@onurtemizkan
Copy link
Copy Markdown
Contributor

Related: epicweb-dev/epic-stack#256

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.

@onurtemizkan onurtemizkan requested a review from AbhiPrasad July 6, 2023 14:06
@AbhiPrasad AbhiPrasad merged commit 5854132 into develop Jul 6, 2023
@AbhiPrasad AbhiPrasad deleted the onur/fix-remix-redirect-responses branch July 6, 2023 14:46
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants