4 ms·
You could load it as an image, as cross-origin policies are not enforced for images. Not sure if their tracker is server-side or requires loading JS.
by bkm 11y ago
You could load it as an image, as cross-origin policies are not enforced for images. Not sure if their tracker is server-side or requires loading JS.
- diggan 11y agoAlso, you should be able to have a proxy on your own domain, changing nothing but the `X-Frame-Options` header.
- dangrossman 11y agoIt's cookies in each user's browser that tell LinkedIn who's viewing a profile. They wouldn't be transmitted to your proxy, so this wouldn't work.
- diggan 11y agoOh, that's true. Good point that I didn't think about at all. Just have done this myself in simple cases where cookies aren't involved.
- aidos 11y agoI've looked at the code - there definitely is some tracking done via XHR requests after the page load. This includes CSRF tokens so you can't hit those tracking links directly. Having said that, we still can't know whether or not the profile view information is harvested from the server-side logging of the main page view or not without testing it.