Looking over many IETF discussion threads, seems like the behaviour of mixing Range and Content-Encoding: gzip is undefined at best. I'm going to disable gzip responses when a Range request is present to prevent this issue.
Looking over many IETF discussion threads, seems like the behaviour of mixing Range and Content-Encoding: gzip is undefined at best. I'm going to disable gzip responses when a Range request is present to prevent this issue.