When submitting a post to the K3B subforum, I continue to get the error message:
---
Content Encoding Error

The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
---
The post does not go through.
Note that I registered and followed up with the registration email message just minutres before my first post. I also logged on and off several times before trying to post.

Which web browser are you using?
Can you email the content of your post to forum-admin@kde.org please?

bcooksley wrote:Which web browser are you using?
Can you email the content of your post to forum-admin@kde.org please?

I'm using IE8.
I just typed in a long reply and lost it again, so I will only reply by email.

I get the same error:
Die Aktion lässt sich nicht ausführen
Details der Anfrage:
Adresse: posting.php?mode=quote&f=9&t=93704&p=189506#preview
Protokoll: http
Datum und Zeit: Samstag 19 Februar 2011 12:06
Zusätzliche Information: Fehlerhafte Daten empfangen
Beschreibung:
Fehlerhafte Daten empfangen

bcooksley wrote:Which web browser are you using?

Konqueror
Version 4.4.5 (KDE 4.4.5)
Unter KDE 4.4.5 (KDE 4.4.5)

bcooksley wrote:Can you email the content of your post to forum-admin@kde.org please?

It's exactly what you see here. The post is sent although the error is shown (I postet the prevew link to avoid double posting...)

bye
TT

I can't seem to reproduce this with reKonq, chrome, FF and IE9.

nor can I duplicate it using Konqueror (openSuse, kde4.6) or IE8 (WindowsXP)

when trying to post i get this:

Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
* Please contact the website owners to inform them of this problem.

TRY AGAIN

I am using firefox 3.6.13

I just posted fine using firefox 3.6.13

are you using some sort of compression addon or 3rd party proxy/secure service to connect to the web?

can you try posting with all firefox addons disabled?

google01103 wrote:I just posted fine using firefox 3.6.13

are you using some sort of compression addon or 3rd party proxy/secure service to connect to the web?

can you try posting with all firefox addons disabled?

i had foxy proxy enabled

tashinorbu wrote:

google01103 wrote:I just posted fine using firefox 3.6.13

are you using some sort of compression addon or 3rd party proxy/secure service to connect to the web?

can you try posting with all firefox addons disabled?

i had foxy proxy enabled

and if you disable it?

i disabled the 3 addons i had and i'll see what happens


and nothing has changed

i i press try again it will post my message twice..

therefore i have to go round trough google and then kde forums....etc....

it never ever happened this to me on any forum...ever...

@tashinorbu even though you disabled the 3 addons are you still connected though a proxy? disabling foxy doesn't disable the proxy - try setting foxy to connect directly with no proxy. what proxy are you using?

This is a quote from another thread:

google01103 wrote:re: "Content decoding error" please join this thread viewtopic.php?f=9&t=93704, are you using any kind of proxy server for ad blocking or compression or whatever?

I'm not using any proxies. Web browsers are configured to connect directly, and the same is configured under KDE's Network Proxy settings.

I do have Adblock Plus for Firefox and Chrome, but even after disabling it, the same error occurs when I try to preview or submit a reply.

I stand corrected! I forgot that Chrome separates each tab into its own process. I loaded up a new instance of Chrome (with Adblock Plus disabled) and now I can preview and submit replies without hassle. Going to try again with Firefox and report back in a few minutes.

I can confirm that the same culprit (Adblock Plus) is behind my "Content decoding error" on both Firefox and Chrome. I disabled it on both, closed both browsers entirely, and then launched both browsers. No issues when I preview or submit replies.

A quick update:
I think I'm going crazy. I re-enabled the Ablock Plus extension on both browsers, but the problem did not return. Was something just recently fixed on the this website's end?