Posted May 19, 2022
lupineshadow: Append a query string to the end of whatever the url is
ht tps://gog-cdn-lumen.secure2.footprint.net/token=nva=XXXXXXXXXXXXXXXXXXXXXXXXXXXX/secure/offline/this/that/theo therxxxxxxxxxxxxxxxxxxxx.exe.xml?timestamp=1652962228
Timboli: Thanks for the info, but unfortunately I don't have the knowledge to use it. ht tps://gog-cdn-lumen.secure2.footprint.net/token=nva=XXXXXXXXXXXXXXXXXXXXXXXXXXXX/secure/offline/this/that/theo therxxxxxxxxxxxxxxxxxxxx.exe.xml?timestamp=1652962228
Any URL can have an optional query string.
It is part of the HTTP protocol.
https://www.rfc-editor.org/rfc/rfc2616#section-3.2.2
A query string is a list of name value pairs separated by ampersands.
These can be accessed by the webserver if asked to by the script running the page.
But if you add redundant name value pairs it doesn't affect anything unless the script explicitly checks for weird query strings and decides it doesn't want to play ball.
Basically any webpage you can add ?favouriteonlinegamingshop=gog&leastfavouriteonlinegamingshop=epic
and it won't affect functionality at all.
If it has a query string already (the start denoted by ?) then change the ? to an & to add extra name-value pairs.
Let's try...
https://www.google.com/search?q=steam
https://www.google.com/search?q=steam&favouriteonlinegamingshop=gog&leastfavouriteonlinegamingshop=epic
As you can see the extra name-value pairs don't affect the page.
But to any proxy servers in the middle it should be a different URL as the proxy servers wouldn't know that the end server doesn't care about that query string (or name-value pairs)
A timestamp (in the previous example a unixtime timestamp) would make the query unique enough unless people's manifest updates run at the exact same second for the same game.
Post edited May 19, 2022 by lupineshadow