-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session Replay networkResponseHeaders is not capturing headers with apollo client #8886
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-replays for triage ⏲️ |
Moved this to our SDK repo as it is likely an SDK issue. |
Is this still an issue? I think we had a UI bug regarding the headers that has been fixed in the meanwhile, could you check again @jsfeb26 ? |
Hello, we're noticing the same issue of missing headers with default browser |
I am still seeing the issue. Would it require an update of the |
@jsfeb26 or @TerencedzLi : Do you use Sentry SaaS? If so, could you provide the link to a replay where you see the incorrect headers? |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Still seeing this issue using on-prem sentry, but it appears to be sporadic for whatever reason |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
We're using
"@sentry/react": "^7.61.0"
and"@apollo/client": "^3.8.1"
. I bumped to this version of apollo client to deal with this #8345.That fixed the
undefined
response body and I thought it would also fix the missing response header but I'm still not seeing the response header.Session Replay Configuration:
Expected Result
There should be an additional response header
x-request-id
Actual Result
I've confirmed the same request in the actual app has the
X-Request-Id
response headerProduct Area
Replays
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: