Firefox 42 x64, zimbra unicode

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
3 years ago
3 years ago

People

(Reporter: velkhor, Unassigned)

Tracking

({64bit})

42 Branch
x86_64
Windows 10
64bit
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

These bug exist when i use java client or ajax client or html client.
This bug exist only in FF 42 x64. On FF 42.0 x86 everything works good.
Tested on two PC, with FF x64.
1. Log in my zimbra mail account (ZimbraWebClient 8.0.7_GA_6021)
2. Create new mail.
3. Type few words, wait for autocomplete.
I check codepage it's Unicode.
there is some bug described bellow.


Actual results:

4. Server send ajax request, and recieve reply:
"...Mariusz W骿cik..." 骿=0x9ABF Unicode Han Character


Expected results:

4. It's should be:
"...Mariusz Wócik..." ó=0x00F3 LATIN SMALL LETTER O WITH ACUTE
(Reporter)

Updated

3 years ago
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Component: Untriaged → DOM
Keywords: 64bit
Product: Firefox → Core
Would you be willing to create HTTP logs of this interaction in both the 64-bit and 32-bit builds following the directions at https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging ?  It's hard to say exactly what your zimbra web client is doing here...
Flags: needinfo?(velkhor)
(Reporter)

Comment 2

3 years ago
Created attachment 8687125 [details]
log x86.txt
Flags: needinfo?(velkhor)
(Reporter)

Comment 3

3 years ago
Created attachment 8687126 [details]
log x64.txt
(Reporter)

Comment 4

3 years ago
Created attachment 8687127 [details]
Zimbra.png - screenshot of post message
(Reporter)

Comment 5

3 years ago
I'm make log, but I can't see thisw post message. I try find ó, or stragne chinese sign, I don't find it.
Right, the log doesn't contain the bytes sent/received, just the headers and some other information.  That's annoying in this case, of course.

Comparing the logs, these look like the relevant parts of the 32-bit log:


2015-11-13 10:01:24.455000 UTC - 0[711140]: http request [
2015-11-13 10:01:24.455000 UTC - 0[711140]:   POST /service/soap/AutoCompleteRequest HTTP/1.1
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Host: zimbra.unknown.com
2015-11-13 10:01:24.455000 UTC - 0[711140]:   User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Accept-Language: pl,en-US;q=0.7,en;q=0.3
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Accept-Encoding: gzip, deflate
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Content-Type: application/soap+xml; charset=utf-8
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Referer: https://zimbra.unknown.com/
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Content-Length: 325
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Cookie: _ga=GA1.2.1722234433.1415027821; ZM_TEST=true; ZM_AUTH_TOKEN=0_aa99a1e72cdbe934b42b1662f2c7b65e2fd2b2e4_69643d33363a38363837383032622d333735312d343630362d393561662d3538346338623663663134313b6578703d31333a313434373538313637393535363b76763d323a31303b747970653d363a7a696d6272613b; JSESSIONID=ot7vxj9lhknmam9sco4pozs5
2015-11-13 10:01:24.455000 UTC - 0[711140]:   X-Token: a5ca75c32edc7708fafc7ba31b2926d6
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Connection: keep-alive
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Pragma: no-cache
2015-11-13 10:01:24.455000 UTC - 0[711140]:   Cache-Control: no-cache
2015-11-13 10:01:24.455000 UTC - 0[711140]: ]

and

2015-11-13 10:01:24.471000 UTC - 11692[711680]: http response [
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   HTTP/1.1 200 OK
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Date: Fri, 13 Nov 2015 10:01:24 GMT
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Server: Apache/2.4.7 (Ubuntu)
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Content-Type: text/javascript; charset=utf-8
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Cache-Control: no-store, no-cache
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Content-Length: 370
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Keep-Alive: timeout=5, max=92
2015-11-13 10:01:24.471000 UTC - 11692[711680]:   Connection: Keep-Alive
2015-11-13 10:01:24.471000 UTC - 11692[711680]: ]

while for the 64-bit log the relevant bits are:

2015-11-13 08:23:48.365000 UTC - 0[233da0e800]: http request [
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   POST /service/soap/AutoCompleteRequest HTTP/1.1
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Host: zimbra.unknown.com
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Accept-Language: pl,en-US;q=0.7,en;q=0.3
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Accept-Encoding: gzip, deflate
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Content-Type: application/soap+xml; charset=utf-8
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Referer: https://zimbra.unknown.com/
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Content-Length: 325
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Cookie: _ga=GA1.2.1722234433.1415027821; ZM_TEST=true; ZM_AUTH_TOKEN=0_6787a91a3790008129b2f3b153430df70b442e2e_69643d33363a38363837383032622d333735312d343630362d393561662d3538346338623663663134313b6578703d31333a313434373537353831323532393b76763d323a31303b747970653d363a7a696d6272613b; JSESSIONID=1fjs2avvp7jmlkw9jst1dzygd
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   X-Token: a5ca75c32edc7708fafc7ba31b2926d6
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Connection: keep-alive
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Pragma: no-cache
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]:   Cache-Control: no-cache
2015-11-13 08:23:48.365000 UTC - 0[233da0e800]: ]

and

2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]: http response [
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   HTTP/1.1 200 OK
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Date: Fri, 13 Nov 2015 08:23:48 GMT
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Server: Apache/2.4.7 (Ubuntu)
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Content-Type: text/javascript; charset=utf-8
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Cache-Control: no-store, no-cache
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Content-Length: 1106
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Keep-Alive: timeout=5, max=99
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]:   Connection: Keep-Alive
2015-11-13 08:23:48.381000 UTC - 11860[233daaac00]: ]

I'm not sure why the two responses are different lengths, exactly, but we certainly seem to be sending the same thing to the server in both cases: same content-length, same content-type, including charset...

If you're willing to try something like wireshark to capture what's actually going on the wire, that might help.  But so far it looks like the server is just sending back different content.
You need to log in before you can comment on or make changes to this bug.