As far as I know, the HTTP standard doesn't require browsers to decode content with a decoding mechanism if and only if it has been specified in the Content-Encoding header. I don't think this is a bug.