Wordpress home tries to download instead of load

HI there,

When one wordpress user tries to load our home page signed in, they get a download file of the html document. Opening the file, its basically an html doc with the follwing header inserted at the top (pasted below_)

It seems to be a Cloudflare issue. I cut a couple of long strings and noted it below, and you can see where the html document starts as normal, after which i snipped.

Can anyone think of an issue that is causing this to happen? seems to only happen on Chrome. It seems to not recognize the start as a header or certificate or something, and to think it should be downloaded instead loaded as an html page

sxg1-b3,äxsig;sig=* [ super long signature string cut here ]=*;validity-url=“.msg.validity”;date=1655816596;expires=1655830996≥CageC165DdateXTue, 21 Jun 2022 14:03:16 GMTDvaryX1Accept-Encoding, Accept-Encoding, Accept-EncodingFcf-[another string cut here]=FserverJcloudflareG:statusC200Gx-cacheDMISSIexpect-ctXWmax-age=604800, report-uri="report-uri/Cloudflare/com/cdn-cgi/beacon/expect-ct"Jcf-apo-viaFtcacheKx-cacheableCbotLcontent-typeXtext/html; charset=UTF-8Lx-powered-byIWP EngineMcache-controlXmax-age=10800, must-revalidateMcf-edge-cacheXcache,platform=wordpressMlast-modifiedXTue, 21 Jun 2022 14:00:04 GMTMx-ca[email protected]<!doctype html>

Normal html doc here

I’ve had three reports today of the same issue affecting some users of my site. Seems to only affect our homepage in Chrome, tested Chrome 102 & 103 on Android & Windows.

I can’t reproduce it personally. My region also wasn’t affected by last night’s Cloudflare outage. Maybe this is related?

We’re experience the same problems with our websites (non-wordpress). I’m personally not able to reproduce this but a college was able to but after removing all the browser cookies the website behaved normal again. Also purging the Cloudflare cache seems to solve it (at least for a couple of hours).

I came across the following, Automatic-Signed-Exchanges-SXGs. We’ve currently disabled the option hoping this will fix the problem but we’re not sure.

Same issue on our website, affecting older chrome browsers, no idea why

When you use the “Pause Cloudflare for this Website” option from the Cloudflare dashboard, does this happen again? :thinking:

I wonder what kind of type of HTTP headers is the web hosting sending and which ones are being presented to Cloudflare, so this happens so far? :thinking:

Are you using some kind of caching plugin for WordPress, or rather some compression, or even the Web hosting uses something?

Thanks for feedback.

are you on litespeed and use wp rocket plugin ?

Some more info here.

We’re not on Wordpress or PHP or using any caching/compression plugins (just gzip). We’re serving a CGI site from Nginx/cgd. No recent changes in relevant configuration.

Some of our users are able to solve this issue by logging out of our site and others are not. We’ve tried purging cache and logging everyone out of our site, no luck.

We reached out to Cloudflare and they asked us for an HAR file to troubleshoot, but unfortunately we haven’t been able to find a cooperate user that’s experiencing this issue yet.

Thanks for raising this - what is happening here is a browser bug that we’re preparing a fix for on our side. The unusual response you’re seeing is actually a valid Signed Exchange (SXG) response, but the browser isn’t parsing it correctly.

The fix is gradually rolling out, but for now if this is causing you a problem please disable the Automatic Signed Exchanges (SXGs) feature under your website speed settings here:


We’ll update here to confirm when the fix is fully released.


I can confirm having the same issue on my WP site with CF PRO. Disabling SXG fixed the issue for now, so I hope it will not show up again.

I am only sad that I reported it with all the information and screenshots to the support. But still got an aswer that they need more info…even if I said that I give all I have. Thats not a great support on paid tier of CF :confused:

hey hi @atack9 would you be able to share the ticket number with us? We will make sure to update that.

of course: 2483267. I alrrady responded that ticket with a link to this thread.

@simon any update on this?

The fix is currently being rolled out worldwide. Once it’s complete - we’ll let you know.

1 Like

I’ve confirmed that a fix for this has rolled out completely now - if you had previously disabled Automatic Signed Exchanges (SXG) you can now safely re-enable.

1 Like

Fantastic thank you

I can’t reproduce it personally. My region also wasn’t affected by last night’s Cloudflare outage. Maybe this is related?

This has been resolved:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.