News for hackers. Stuff that matters.
Re:Sourcebuster.js by chimen on Sunday March 03, 2019 @03:50PM (#19296765)
I don't get the point of this in a client script. What does it do that can't be done server side with the http headers? Maybe it can be useful inside SPAs but this sort of info should be immutable and read only which is next to impossible on front facing apps.
Re:Sourcebuster.js by buremba on Sunday March 03, 2019 @04:25PM (#19297007)
You can still emulate the Referer header in order to trick the server side. It's easier to do this on the client side in order to avoid complexity on server-side because the servers need to be aware of all the browsers used by the client.
Re:Sourcebuster.js by chimen on Sunday March 03, 2019 @06:55PM (#19297738)
Makes no sense. What complexity are you talking about? You get that info on the client to create another request to the server in order to send it over?
Re:Sourcebuster.js by buremba on Monday March 04, 2019 @03:24AM (#19299649)
Unless you're only tracking the pageview events, it's not an additional request. Most of the analytics SDKs use either XHR or Pixel tracking. It's often easier to build up a separate analytics pipeline rather than using the backend server logs.