{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
dazarobboにより編集済み:
8/11/2014 2:13:55 PM
3
In all seriousness though, they probably have collected information on who has clicked to open this topic. It would be trivial too, assuming you weren't using https://www.bungie.net/ and were only using http://www.bungie.net/.
Edit: actually, even if you were using HTTPS, they could still see even without cracking or having access to the SSL key.
English
-
dazarobboにより編集済み: 8/12/2014 5:27:44 AMHTTP = clear text. Any time you request a web page, the request itself is sent "in the clear", meaning anyone who has access to the infrastructure between your device and the web server can read it and the web page which is returned to you. HTTPS = encrypted. Same as HTTP except the request and the response (the web page) is encrypted so the same people/organisations who might have access can't/will find it extremely difficult to read the original data. The reason why it's not working properly on bungie.net is because [some of] the pages contain resources from halo.bungie.net which, when requested, aren't done so using HTTPS. That subsequently means that when those resources are requested, the request will have a [url=https://en.wikipedia.org/wiki/HTTP_referer]Referer header[/url] set pointing to the HTTPS page the request originated from, and thus making it publicly known who is requesting which page even when HTTPS is used. Edit: I was wrong. This isn't true. However, if a remote resource is using HTTPS along with the original page, the referer is set.
