There is some misguided use of 501 Not Implemented status to complain when the client asks for range requests in scenarios which are not supported. I think there are separate cases to consider:
We don't want to support it: just return 200 OK with full response
It is malformed: return 400 Bad Request?
It is unsatisfiable: return 416 Requested Range Not Satisfiable
none of these are particularly relevant to well behaved clients, but it seems we have encountered bad clients who send Range headers on resources where we do not advertise support via Accept-Range.
There is some misguided use of 501 Not Implemented status to complain when the client asks for range requests in scenarios which are not supported. I think there are separate cases to consider:
none of these are particularly relevant to well behaved clients, but it seems we have encountered bad clients who send Range headers on resources where we do not advertise support via Accept-Range.