Do not update/delete: Banner broadcast message test data
Do not update/delete: Notification broadcast message test data
Fixes #562 (closed).
While we're doing the HEAD request, we also get the etag sent back from the server for caching purposes. In the past we had a more typical workflow of:
The reason we don't do this any more is that it allows for servers to send custom etags to different users and thus track downloads made by each user. Thus now we only ever ask for etags and then do our own comparison, rather than sending etags and letting the server decide if they match or not.