Currently, the user's browser will connect directly to my server in order to report in.
That means that access logs on my side will contain the user's IP - that could then be correlated back to a point.
I want to make sure the solution allows us to abstract that away, by serving via CDN.
www.bentasker.co.uk (for example) is already served by a CDN, so this wouldn't be a case of involving a third-party unnecessarily: they're already party to comms to/from the user.
Activity
18-Dec-21 12:26
assigned to @btasker
18-Dec-21 12:26
^ fat fingers
18-Dec-21 12:28
The aim of this issue is two-fold really.
Serving the JS agent via CDN is obviously no issue, but want to make sure there's nothing we're doing which'll negatively impact the
POSTin.Secondly though, it serves as a sort of marker for future improvements. If we were to start using cookies to track things (like, for example page views in #4), it'd enable cross-domain tracking (because the agent is coming from a common domain), which is explicitly against the aims of this project.
29-Dec-21 11:00
I've been back around the block on this.
Serving via the CDN means some additional latency for writes (because there are now 2 hops), but it gets the agent served quickly as well as moving the client's writes away from being directly to my system.
I'm serving
pfanalytics.bentasker.co.ukvia CDN, and it seems to be working quite well so far.29-Dec-21 11:01
mentioned in issue #4