4 ms·
That's not how that works. Very simplified, but the HTTP workflow is: 1. Client requests document (GET) at /hello_world from xyz.com 2. Server responds with
by kodah 4y ago
That's not how that works.
Very simplified, but the HTTP workflow is:
1. Client requests document (GET) at /hello_world from xyz.com
2. Server responds with status code and document (or empty)
The server absolutely has an opportunity to log any part of the request.
- revskill 4y agoWhen i said tracking, it's not just logging. They know nothing except for all browser information.
- kodah 4y agoI said logging because that's what I usually do with this information, but if your goal is track then you can do it with the same information. Fingerprinting can happen actively (with JS) or passively (without JS). The former is obviously more precise, the latter isn't bad at all. In passive fingerprinting you can combine the IP, which is a connection IP - nothing to do with HTTP, and the User-Agent header. You are now tracked.