Sitemap could not be read

There is weird behavior of your server. It forces gzip compression even if browser doesn’t request this kind of compression.

Example:

$ curl -i -H 'Accept-Encoding: br' https://nnnnnnnnnnnn.com/sitemap_index.xml
HTTP/1.1 200 OK
Server: Sucuri/Cloudproxy
Date: Wed, 03 Apr 2019 15:20:24 GMT
Content-Type: text/xml; charset=UTF-8
...
Content-Encoding: gzip
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Cache-Control: max-age=315360000
X-Sucuri-Cache: HIT

O??0?????Z
...
$ curl -i https://nnnnnnnnnnnn.com/sitemap_index.xml
HTTP/1.1 200 OK
Server: Sucuri/Cloudproxy
Date: Wed, 03 Apr 2019 15:21:49 GMT
Content-Type: text/xml; charset=UTF-8
...
Content-Encoding: gzip
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Cache-Control: max-age=315360000
X-Sucuri-Cache: HIT

O??0?????Z

Please notice other issue – max-age=315360000 (10 years). I think that’s too long.

@jounin Please create new topic with more details (eg. sitemap URL).

The max age is coming from my HSTS setup

# BEGIN Really_Simple_SSL_HSTS
<IfModule mod_headers.c>
Header always set Strict-Transport-Security: “max-age=31536000” env=HTTPS
</IfModule>
# END Really_Simple_SSL_HSTS

I had to use an online sitemap generator then upload it using filezilla Google is now accepting is https over http.

I still would like to get Yoast sitemaps to work thought as manually generating this will become a pain really soon.

I am wondering if sucuri is causing the compression or if its Really Simple SSL’s implementation of HSTS

I still see weird behavior related to compression, … It seems that your website is behind Sucuri Firewall/Cache. It’s possible that some rules in .htaccess and Really Simple SSL (HSTS) doesn’t work good in combination with “Sucuri proxy”.

This thread has been marked as resolved due to lack of activity.

You’re always welcome to re-open this topic. Please read this post before opening a new request.

Thanks for understanding!