Just made a post from a Win XP system running Firefox, got a page full of wierd "wingdings"-ish nonsense in response but the post seems to have gone through anyway.

It doesn't seem to be possible to submit an edited post. Update just returns to the same screen?

Quick reply worked fine.

FWIW the mess I saw looked like a HTTP header so what followed might have been text in the wrong encoding or compressed.

Yes it was sent "GZIP" compressed. It happens for full reply but not quick reply. Could be an XP only thing though?

HTTP/1.1 200 OK Date: Tue, 29 Mar 2016 08:32:53 GMT Server: Apache/2.4.7 (Ubuntu) Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache X-Powered-By: e107 Vary: Accept-Encoding Set-Cookie: cfukcookieSID=***; expires=Tue, 29-Mar-2016 09:32:54 GMT; Max-Age=3600; path=/ ETag: "60afcb2305e32edda537dfe3ee4c8bc8-gzip-gzip" Content-Encoding: gzip Content-Length: 6570 Keep-Alive: timeout=5, max=96 Connection: Keep-Alive Content-Type: text/html; charset=utf-8 ��]{w۶���:'�
Q6�}�z�/�V��

OK trying posting from home to see if the same thing happens, also after posting I will go back and try to edit the post

Successful edit, though after the edit I get the same wierd output

Boriseng: could you attach some screenshots please? I'll pass them on to the e107 dev.

Here's an example. I was in a paranoid mood yesterday so I painted out the session cookie.

I thought I'd try to figure it out myself but I can't follow the page structure. Firefox only seems to have "View source". I can see the source for the sidebars but not the center panel.

Maybe I'll try a different browser later.

My guess is that the code that adds the HTTP header is getting called twice and the first header is taken as the real one so the second header gets displayed as text. This might be a diagnostic/debug thing.

Boriseng, issue raised here https://github.com/e107inc/e107/issues/1476#issuecomment-203568433. Thanks

I think I see, compressing text responses is obviously a good thing but it could be done by either the forum or the server but not both.

Although it is worth mentioning that it only happens under specific circumstances (e.g. posting and editing) and doesn't occur while browsing or making quick posts.
Also I haven't tested other browsers yet. I was going to but got distracted last night.

Posting from Internet Explorer this time. Also note that the "Log In" menu option gave a blank screen with nowhere to enter stuff. The top left hand log-in button worked though.

...and no weird response it just went back to the topic.
...so back to firefox...

Seems OK now in IE and FF under Win7

Just checking...OK? No still spits out weird stuff in FF