Repository navigation
Handle Apollo multipart failed-request inspection safely #5987
Description
Context
The Apollo 4 and Apollo 5 integrations inspect HTTP response bodies to detect GraphQL errors. Multipart and incremental responses need separate handling so inspection does not buffer, block, or consume streaming bodies.
Scope
- Define safe failed-request inspection for multipart/incremental responses in
sentry-apollo-4andsentry-apollo-5. - Preserve spans and breadcrumbs when body inspection is skipped or unsupported.
- Decide between skipping failed-request body inspection for multipart responses and parsing multipart parts for GraphQL errors.
- Add tests covering streaming behavior and body preservation.
WebSocket subscription instrumentation remains out of scope.
Activity
linear-code commentedon Aug 25, 2026
JAVA-703
adinauer commentedon Sep 1, 2026
We should treat this as a bug since adding Sentry to Apollo breaks the
@deferand@streamfeatures which use multipart responses. We considered adding an option to control whether to inspect multipart requests but decided against it since that means you're choosing at compile / release time whether to use or break the features. Broken defer/stream may mean the customers UI loads very slowly or worst case indefinitely.We decided to no longer inspect the response body of multipart responses for errors.
github-actions commentedon Nov 11, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #6432, which was included in the 8.64.0 release.