Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
A user reported that when their settings include the networkDetailAllowUrls integration, the requests to an example domain cease to appear in the Sentry network requests tab during a replay:
When the user has their setting as:
integrations: [
new Replay(),
],
Then the domain requests show up (just no body).
As soon as the user specifies networkDetailAllowUrls
, their example domain requests will stop showing up. So, a config like this makes the domain requests disappear from the Sentry network requests tab in a replay:
integrations: [
new Replay({
networkDetailAllowUrls: ['exampledomain.io']
}),
],
It's important to note that the issue may be related to how the Replay integration handles query parameters in the URL, particularly those involving URLs because it doesn't filter all domains added to the integration.
Please see Jira Sync for more information.
Expected Result
When the Replay integration includes the configuration parameter networkDetailAllowUrls: ['demodomain.io'], it is expected that requests to 'demodomain.io' should be visible in the Sentry network requests tab during a replay. Specifically, the integration should allow the specified URL to be processed without being blocked, ensuring accurate and complete replay of network requests.
Actual Result
Currently, when the networkDetailAllowUrls parameter includes 'demodomain.io', the requests to the specified URL with a URL as a query parameter are blocked. As a result, these requests do not appear in the Sentry network requests tab during a replay, leading to incomplete network data.
This behavior contradicts the expected functionality of the Replay integration, indicating a potential issue or bug in the integration logic.
Product Area
Replays
Link
No response
DSN
No response
Version
No response
┆Issue is synchronized with this Jira Improvement by Unito
Metadata
Metadata
Assignees
Type
Projects
Status