You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in the process of setting up "user tracking" for an internal tool, part of this sends the most recent path to Pusher.
However, I'm not aware of any way of detecting if an action has been initiated as part of a "prefetch" visit or not.
It would appear that HTTP_X_SEC_PURPOSE is set to prefetch even on a full click event (I suppose it is an event that was prefetched before committing to the click).
Unless I can differentiate between the two I guess the options remaining are to disable prefetching with <meta name="turbo-prefetch" content="false"> or to implement this in the frontend when the page changes
The text was updated successfully, but these errors were encountered:
I'm in the process of setting up "user tracking" for an internal tool, part of this sends the most recent path to Pusher.
However, I'm not aware of any way of detecting if an action has been initiated as part of a "prefetch" visit or not.
It would appear that
HTTP_X_SEC_PURPOSE
is set toprefetch
even on a full click event (I suppose it is an event that was prefetched before committing to the click).Unless I can differentiate between the two I guess the options remaining are to disable prefetching with
<meta name="turbo-prefetch" content="false">
or to implement this in the frontend when the page changesThe text was updated successfully, but these errors were encountered: