The EULA isn’t null and void, but it’s pretty meaningless. Not because you can’t reasonably be expected to copy that link into a browser to read it, but because there’s no indication that you should or even must do that.
The EULA contains no terms, it doesn’t contain any wording saying what you can or can’t do. It doesn’t say what your rights are. It just contains something that looks like a URL. So, you’re still bound by the terms of the EULA (as much as you’re bound by any EULA) but the EULA doesn’t permit or forbid anything. It’s effectively the same as if it were blank.
The site at the end of that URL will set a cookie. How else would such a mechanism be functional at all? A call to steams naviagtionTiming api confirming the last page load and nothing else at all? Hard to imagine a product manager agreeing to such a pointless exchange. So it cant be redirected to an ip, which I assume you mean is running its own webserver on loopback:443. It also implies the mechanism to verify allows cross site scripting, at least to that one other domain.
I bet you could argue in court that the EULA is null and void, because you can’t be reasonably expected to copy that link into a browser to read it
The EULA isn’t null and void, but it’s pretty meaningless. Not because you can’t reasonably be expected to copy that link into a browser to read it, but because there’s no indication that you should or even must do that.
The EULA contains no terms, it doesn’t contain any wording saying what you can or can’t do. It doesn’t say what your rights are. It just contains something that looks like a URL. So, you’re still bound by the terms of the EULA (as much as you’re bound by any EULA) but the EULA doesn’t permit or forbid anything. It’s effectively the same as if it were blank.
Modify your host and redirect the URL > 127.0.0.1. software without license:D
The site at the end of that URL will set a cookie. How else would such a mechanism be functional at all? A call to steams naviagtionTiming api confirming the last page load and nothing else at all? Hard to imagine a product manager agreeing to such a pointless exchange. So it cant be redirected to an ip, which I assume you mean is running its own webserver on loopback:443. It also implies the mechanism to verify allows cross site scripting, at least to that one other domain.