Just thinking: From a client's standpoint could the "large download" traffic correlation be avoided if the client split the large download into multiple HTTP re

Just thinking: From a client's standpoint could the "large download" traffic correlation be avoided if the client split the large download into multiple HTTP requests (assuming the server supports that) that are about as large as a regular webpage request with random delays in between so that it looks like normal web noise? Of course, it'd take wayyy longer to download but wouldn't this make the traffic indistinguishable from page requests?