Rule 34 - Problems with the "mail-system"

Zulgore

02/24/17 06:53PM

Problems with the "mail-system"

Recently my messenger seems to be a bit broken...

More and more often only empty messages reach my conversation partner while i definitly typed a text.
Any1 experiencing somehing similar, or maybe even knows a solution? It's a bit annoying tbh...

dr8rd

02/24/17 07:07PM

There's a word limit. Delete some of the conversation history and try again.

Zulgore

02/24/17 07:12PM

hmmm...no, that's definitly not the problem. Occured also on completly new conversations. Also there's no real "pattern"...sometimes it happens, and sometimes not. Right now i'm fixing it with starting a completly new conversation.

Killua

02/24/17 07:30PM

Mozilla firefox?

Zulgore

02/24/17 07:31PM

Yes!

Killua

02/24/17 07:35PM

Ha! Its a problem that has been around for 2 years and i reported it more than once. Firefox is the only browser so far having that problem. I have not yet been able to identify the problem. Chrome however works just fine.

Zulgore

02/24/17 07:40PM

Thanks a lot mate!

Killua

02/24/17 07:44PM

For all those who will ask: No its not the cookies. That sometimes is a temporary fix but not for long. Sometimes it works for half an hour, sometimes its just 4 minutes.

Open for suggestions.

RhythmMelody

02/24/17 08:57PM

Had the problem too and I'm not using firefox but chrome. Though it didn't happen for quite some time.

bipface

02/25/17 04:45AM

I managed to reproduce it:

I found that whenever I typed an ellipsis (…) character in the messaged body, the sent message is blank. Presumably some other non-ascii characters trigger this too, but ellipsis is the only one I regularly use.

However, this only seems to happen when you're replying to an existing message. If you instead use the Create Message button it doesn't seem to happen.

Let me know how closely my diagnosis corresponds with your case.

Killua

02/25/17 08:59AM

While that is a good idea..Did it actually lead to multiple messages being blank bipface?

bipface

02/25/17 09:05AM

Killua said:
While that is a good idea..Did it actually lead to multiple messages being blank bipface?

Yes, I've lost hundreds of words to this bug. Took me ages to work it out.

Kielan

02/26/17 02:52AM

bipface said:
I managed to reproduce it:

I found that whenever I typed an 1 (…) character in the messaged body, the sent message is blank. Presumably some other non-ascii characters trigger this too, but ellipsis is the only one I regularly use.

However, this only seems to happen when you're replying to an existing message. If you instead use the Create Message button it doesn't seem to happen.

Let me know how closely my diagnosis corresponds with your case.

I tried to re-create the issue using firefox and chrome with ellipsis in a reply and it worked fine for me, no problem at all :/.

bipface

02/26/17 03:34AM

Kielan said:
I tried to re-create the issue using firefox and chrome with ellipsis in a reply and it worked fine for me, no problem at all :/.

I just tested it again, and it's still happening consistently for me with Firefox 50.1

However, I found that it doesn't occur when I send messages from Chrome 43. Upon closer inspection I discovered that FF and Chrome seem to have slightly different ways of encoding their POST parameters:
gist.github.com/bipface/72baac7a211fab1cf4710ecffa9d757c
Firefox's request looks rather buggy. The 'body' parameter is basically empty and the raw text has pieces of HTTP header in it.

I'll see what else I can discover

Kielan

02/26/17 04:08AM

bipface said:

Kielan said:
I tried to re-create the issue using firefox and chrome with ellipsis in a reply and it worked fine for me, no problem at all :/.

I just tested it again, and it's still happening consistently for me with Firefox 50.1

However, I found that it doesn't occur when I send messages from Chrome 43. Upon closer inspection I discovered that FF and Chrome seem to have slightly different ways of encoding their POST parameters:
gist.github.com/bipface/72baac7a211fab1cf4710ecffa9d757c
Firefox's request looks rather buggy. The 'body' parameter is basically empty and the raw text has pieces of HTTP header in it.

I'll see what else I can discover

I'm using the same version of Firefox 50.1 on Windows 10 and get no issue, weird I cannot re-create the issue.