What is a key limitation of the HTTP protocol when transferring files?

The key limitation of the HTTP protocol when transferring files is that the entire file must finish downloading before it can be viewed. This behavior is due to the way HTTP, as a stateless protocol, handles data transmission. When a file is requested, the server sends the file data to the client, and the client cannot begin to process or view the file until it has received the complete set of data.

This limitation is particularly relevant for large files, such as videos or high-resolution images, where users often prefer to preview content while it is still downloading. In contrast, some other protocols or streaming methods allow for partial data to be viewed, enabling a more efficient and user-friendly experience.

Other options do not accurately represent limitations of the HTTP protocol. While HTTP can indeed handle different file types, it does not restrict itself to just text-based files, nor does it impact the quality of the files being transferred. Users also may be able to begin interacting with files in certain formats, like images, before the complete transfer if properly designed with appropriate protocols, but that is not the case with standard HTTP file transfers where complete data reception is necessary for proper use.