[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18768 [Analysis]: Calculate the fraction of dist.torproject.org traffic for Tor Browser downloads and updates
#18768: Calculate the fraction of dist.torproject.org traffic for Tor Browser
downloads and updates
----------------------+---------------------
Reporter: karsten | Owner:
Type: task | Status: new
Priority: Medium | Milestone:
Component: Analysis | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
----------------------+---------------------
Comment (by gk):
Replying to [comment:3 karsten]:
> Sure, we can include number of requests. But does a single Tor Browser
instance only make exactly 1 request to update to a new version, or does
it make several of those? That might make it difficult to compare the
numbers.
It checks periodically whether there is a new update available. But once
it determines there is indeed one out there then it should fetch just one
.mar file in the vast majority of cases. That's why I was explicitly
asking for the requests responsible for the downloads, e.g. those
requesting the .mar files.
Do we understand the nature of the other requests? 38% sounds quite like a
non-negligible fraction. Could they come form things like
https://www.torproject.org/dist/torbrowser/update_2/hardened/Linux_x86_64-gcc3/6.0a4-hardened/ALL
which are the update checks I talked about above (and which should get an
update.xml file back as an answer)?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18768#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs