3 ms·
BRB going to change all my tracking query strings to get around this. don’t be mad at me my OKR is getting tracking to work 2% better.
by haburka 4y ago
BRB going to change all my tracking query strings to get around this. don’t be mad at me my OKR is getting tracking to work 2% better.
- tshaddox 4y agoYou should add an extra query param containing a MAC that is required to be present and correct for the URL to load. Just kill the normal idea of web URLs altogether.
- warkdarrior 4y agoI believe the RFCs do not require URLs to have any editable structure to them (beyond host+port+path+query). In particular the path has no particular semantics and the path+query can hold any values that the server accepts. So the server can define a URL to be well formed in any way they want. Editing a URL on the client is a historical accident at best.
- tshaddox 4y agoIndeed, but my point is more about the assumption that a URL to a public web page is shareable. I don't know that this is every explicitly mentioned in any of the RFSs, but it seems like an undeniable assumption given that the point is for it to be a resource locator. Technically one of these URLs with tracking and a MAC should still be shareable, I suppose, but the tracking would be useless. Webmasters could go even further and generate one-time-use URLs for every page load in every session. They would still technically be URLs, but similarly would be pretty clearly in opposition to the point of URLs.