Http response with "Content-Encoding: gzip", but the content is not gzipped

1
votes

I have a question regarding gzip. Suppose the server adds the “Content-Encoding: gzip” header. But, the actual content is not gzipped (assuming the compression failed and it is sending the data without compression). What will be the impact of this? How will http clients (especially browsers) handle this?

Thanks, Narendra

1
httpgziphttpresponsecontent-encoding

1 Answers

1
votes

The HTTP specifications state that the Content-Encoding response header specifies the encoding to be used to decode the content. However, it doesn't state what client should do in case of encoding mismatch. So it's up to the clients to decide.