Opened 3 years ago

Last modified 12 days ago

#16029 new defect

Many update downloads for 4.0.8

Reported by: mikeperry Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-updater
Cc: mcs, brade Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

While looking through our logs for #15706 and #16028, I also noticed many requests for the 4.0.8 MARs:

$ grep ".mar " dist.torproject.org-access.log-20150514 | grep "GET /torbrowser/4.0.8/" -c
11909

How are these clients deciding to download the old 4.0.8 update?

I see about 15 requests to the old v1 update URL, and another 81 to the pre-channel v2 urls, but those are all telling users to install some non-existent alphas..

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by mcs

Strange. Is there an error in our .htaccess file? That seems unlikely. Is there any discernible pattern related to platform or language?

comment:2 Changed 3 years ago by mcs

I pulled down all of the files under https://dist.torproject.org/torbrowser/update/ and under https://dist.torproject.org/torbrowser/update_2/ and grepped for 4.0.8/ but I did not find anything. Is it possible those GET requests are not from the browser/update service but from something that is crawling or mirroring the files?

comment:3 Changed 3 years ago by mikeperry

This is tapering off over the past few days:

$ zgrep ".mar " dist.torproject.org-access.log-20150515 | grep "GET /torbrowser/4.0.8/" -c
9195
$ zgrep ".mar " dist.torproject.org-access.log-20150516 | grep "GET /torbrowser/4.0.8/" -c
8204
$ zgrep ".mar " dist.torproject.org-access.log-20150517 | grep "GET /torbrowser/4.0.8/" -c
7388
$ zgrep ".mar " dist.torproject.org-access.log-20150518 | grep "GET /torbrowser/4.0.8/" -c
5773

One guess is that this may be the tail end of users who have repeatedly failed the 4.0.8 update due to #15857 or some other #16028-related issue?

comment:4 in reply to:  3 Changed 3 years ago by mcs

Replying to mikeperry:

This is tapering off over the past few days:
...
One guess is that this may be the tail end of users who have repeatedly failed the 4.0.8 update due to #15857 or some other #16028-related issue?

Tapering off is good. The counts are kind of high to be explained by people still in the middle of an old download, but it is difficult to know for sure. Do we need to keep 4.0.8 on the server? Should we rename or remove the /torbrowser/4.0.8 directory? That might force a failure and hasten the movement to 4.5.1.

comment:5 Changed 12 days ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.