I've heard the update checkers in Firefox/Thunderbird also do some additional checks to see whether or not you can run a certain update for other reasons (hardware/software, such as stopping Win9X/ME users from updating FF past a certain point). Maybe there's another reason other than some sort of block at the update servers for my FF not 'seeing' the newer versions. v17-19 do act very strange on my Puppy setup, after all, though it's surprising it never throws any sort of error message.
I'd think if it was a matter of being unable to access the update server, Firefox would at least display a simple error message, in that regard. (Also, wasn't there an extension to change the update server, or was that just to switch update channels?)
Edit: Okay, semi-long day.
Here's the app.update.url value:
Code: Select all
https://aus3.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
Code: Select all
# netstat -tn
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 172.16.1.38:34835 205.188.13.78:443 ESTABLISHED
tcp 0 0 172.16.1.38:35882 72.21.91.19:80 TIME_WAIT
tcp 0 0 172.16.1.38:39596 173.194.79.125:5222 ESTABLISHED
tcp 0 0 172.16.1.38:56601 205.188.4.127:443 ESTABLISHED
tcp 0 0 172.16.1.38:42020 64.12.104.224:443 ESTABLISHED
tcp 0 0 172.16.1.38:47092 66.196.121.24:5050 ESTABLISHED
tcp 0 0 172.16.1.38:54133 65.55.71.43:1863 ESTABLISHED