Posted on 15/10/2025 15:34:38
Hi Rene
I cannot reproduce this issue - I can do what you do using an installation out of the cloud.
That error — ERR_CONTENT_DECODING_FAILED 200 (OK) — is usually a sign that the browser received a compressed response (gzip, deflate, etc.) but the content wasn’t actually compressed, or vice versa. In other words, the headers and the actual data don’t match.
Since this is happening in Visual Editor mode in your local Swift 2 setup, here are the most likely culprits:
IIS / Kestrel compression mismatch
If your local environment (Kestrel or IIS Express) is configured to use compression, and the Visual Editor request (Default.aspx?visualedit=true) somehow double-compresses or misreports compression, Chrome will throw that decoding error.
Fix:
Try disabling response compression in appsettings.json or IIS for localhost to test:
"ResponseCompression": { "EnableForHttps": false }
Or temporarily disable it from IIS Express settings.
Middleware interference
If there’s a reverse proxy (like IIS Express → .NET app) and both layers try to apply gzip compression, you get the mismatch. Sometimes UseResponseCompression() in .NET combined with IIS compression causes this.
