DEV: Add X-Discourse-BrowserPageView response header #33598
+19
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we are tracking requests in the
Middleware::RequestTracker
, wehave historically added an
X-Discourse-TrackView
response headerfor implicitly tracked requests, which are HTML requests.
Within the past couple of years, we introduced the concept of
Browser Page Views (BPVs), which are also known as explicitly tracked
requests, which are recorded when requests are made via AJAX.
These also add the
X-Discourse-TrackView
header to the response,so it is hard to differentiate the two in logs.
This commit adds a new response header,
X-Discourse-BrowserPageView
,that acts in a similar way to the existing
X-Discourse-TrackView
header, but is specifically for requests that are tracked as BPVs.
AJAX call:
HTML page load: