Yeah, that's fair, but is likely a corner case. How often do you see a finitely sized resource that doesn't get returned with a Content-Length response header?

Yeah, that's fair, but is likely a corner case. How often do you see a finitely sized resource that doesn't get returned with a Content-Length response header? If push came to shove, a browser could simply stop reading & close the connection after consuming a certain number of bytes. GIFs are sequential things anyway, aren't they? I don't remember that detail.