Unsupported Content-Coding: none

[JFossey]

Hi,

I have recently revamped a pre-existing website developed in Yii using GravCMS.

When I have look to test the site using using tools like W3C validator and Chrome dev tools I get and error "Unsupported Content-Coding: none".

When I look into this issue I find Content-Encoding header can take only five values: gzip, compress, deflate, identity, br. The “none” is therefore an invalid value.

Ref:

• Related Issues: "Content-Encoding: none" breaks mod_deflate #548
• Related Docs: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding

[JFossey]

Just to follow up on this, the only workaround I found thus far is the following settings.

• Gzip compression = YES
• Allow WebServer Gzip = NO

[rhukster]

Thanks for researching this. I am going to add this to the troubleshooting section of the learn site.

[mahagr]

The issue is caused by this line:

https://github.com/getgrav/grav/blob/develop/system/src/Grav/Common/Grav.php#L442

I think there was a reason why we ended up using none as the value; I think it prevents webserver from compressing the request.

[JFossey]

I looked for an alternative way of preventing gzip compression and found the following.
Hope it helps. The apache set env looks promising for many common setups.

function disable_gzip() {
	@ini_set('zlib.output_compression', 'Off');
	@ini_set('output_buffering', 'Off');
	@ini_set('output_handler', '');
	@apache_setenv('no-gzip', 1);	
}

[mahagr]

@JFossey Can you test out the change?

[JFossey]

@mahagr I have not yet tested it out, but I will, it just might be a while before I get round to this.

[JFossey]

@mahagr This seems to work as intended, thank you.