I am serving mp3s with a minimalistic nginx server. What I see in my log files is that there are a lot of requests, in particular from AppleCoreMedia and sometimes Android useragents, that flood the server with short requests. Sometimes they keep requesting to download the same partial content for a very long time; sometimes more than an hour. For example:
"GET /somefile.mp3 HTTP/1.1" 206 33041 "AppleCoreMedia/184.108.40.206B206 (iPhone; U; CPU OS 5_1_1 like Mac OS X; en_us)" "GET /somefile.mp3 HTTP/1.1" 206 33041 "AppleCoreMedia/220.127.116.11B206 (iPhone; U; CPU OS 5_1_1 like Mac OS X; en_us)" "GET /somefile.mp3 HTTP/1.1" 206 33041 "AppleCoreMedia/18.104.22.168B206 (iPhone; U; CPU OS 5_1_1 like Mac OS X; en_us)" [...]
I also get a lot, but not as much, of these:
"-" 400 0 "-" "-" 400 0 "-"
The IP addresses are always from clients that start downloading shortly after that request, usually they have roughly the same UserAgent as in the first example. emphasized text I have enabled server throttling and connection limits in nginx to limit the huge amount of log entries from equivalent IPs at least somewhat.
There was a performance issue when I saw the same behaviour on the previous server that used Apache. I installed nginx on a better server then moved the site. When Apache could not handle more connections from the increasing number of clients effectively that server was ddossed. There was no bandwidth issue with already connected clients and I don't know if the already connected clients were using more than one connection at a time.
Please tell me:
- Are clients that appear to get stuck on a download a Bad Thing™
I heard people say their mobile bandwidth use was much higher than they could account for. I'm thinking this type of client behaviour can account for that. And costs us more bandwidth too.
- Which up to date alternatives exist out there that can handle serving this type of data better than plain HTTP?
- Useful general insights for someone who just came into this field straight out of the late 90s. :-)