Hi,
In general, this is the intended behaviour. For internal usage,
Chromium Updater checks whether there exists a network connection for
the reason to stop any other processing once no connection is
available. Probably there would be better options than using the built-
in version check for that, I guess, but I decided to run that routine,
because it also makes sure that the update server is available at that
time.
For the redirection, I will look into that one for the next update.
This is probably an issue, because the Chromium project often changes
download locations on its servers, sometimes simply by redirecting old
paths to the new ones and sometimes even without doing so, what means,
I have to change them manually within Chromium Updater.
Thanks for your report. I'll try to include your findings within the
next update, perhaps I will find a way to reduce network usage a bit.