Major We need to disable ETag header behavior in DownloadService for blob without digest because it could leads to cache issues.
This is due to usage of blob's digest in the ETag header of HTTP response. When digest is null ETag equals to "null" then further requests to same url will have this value in If-None-Match header which will trigger a HTTP 304 code response as it matchs the null digest even if file has changed.
Log when it happens.
Problem found in NXP-19564.
