Repository navigation
Streamed http.client spans have different url.full and http.url attribute values #21639
Description
These attributes should have the same values (with http.url being deprecated), but it seems like they carry different URLs (host page vs. fetch request URLs?)
Example event: https://sentry.sentry.io/explore/traces/trace/079b7f956bdf49ab90f22219e3bda5d3/?node=span-b24f99cb80594e7d&project=4505160012660736&query=span.description%3A%22POST%20https%3A%2F%2Fgibpotato.app%2Fcollection%22&source=traces&statsPeriod=14d&targetId=b24f99cb80594e7d×tamp=1781019734
Metadata
Metadata
Assignees
Projects
- Status
Activity
linear-code commentedon Jun 18, 2026
JS-2808
[-]Streamed `http.client` spans have different `url.full`and `http.url` attribute values[/-][+]Streamed `http.client` spans have different `url.full` and `http.url` attribute values[/+]suzunn commentedon Jun 19, 2026
I would start by tracing where the streamed span gets its legacy
http.urlvalue versus the newerurl.fullvalue, then force both attributes to be derived from the same normalized request URL at span creation time. The regression test should cover a streamed response where the page URL and fetch URL differ, because that is the shape that would catch an accidental fallback to the current browser location or request context. Keeping the deprecatedhttp.urlas a compatibility alias is fine, but it should be written from the same source asurl.fulluntil it is fully removed.fix(browser): Ensure `url.full` and `http.url` attributes have the sa…
github-actions commentedon Jun 23, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #21660, which was included in the 10.60.0 release.