Search results

Great, and yes, we'll accept a 200 response for the Range request.

Hi @mistwang, I'm actually reporting this on behalf of Facebook, so won't be able to upgrade any implementations. I will refer bug reporters to this thread though. Would you be able to have someone verify if the bug could present itself as described in this thread?

Hey @mistwang, although you might be right about LiteSpeed being self-consistent, this is an issue that we are only seeing with LiteSpeed servers. Attached is another sample: $ curl -v --compressed -H 'Connection: close' -H 'Range: bytes=0-524288' -A "facebookexternalhit/1.1...

When combining `Accept-Encoding: deflate, gzip` and `Range: bytes=0-524281` as request headers, the response, both gzipped and limited to the range, is returned with a missing `Content-Encoding` header. This causes Curl and other clients to fail to decode the response. oyvind-mbp:~ oyvind$ curl...