Apache Reverse Proxy causing mangled characters in some ZM js files...

[gutow]

I am trying to set up a reverse proxy using Apache to forward my ZM server through my SSL gateway. I have other things such as Plone instances working fine this way.

When I try to proxy the ZM machine I get characters mangled in some of the js files. Thus things do not work. My other backend servers do not have this problem. One specific example is line 389 of skin.js:

const cookie = getCookie('zmFilterBarFlip'+this.attr('data-flip-control-object'));

where the 'c' in 'cookie' appears to be changed to control C (U+0081). I tried making sure that the encoding for the js files is not changed by the proxy. Is there something funny about some of the 'c' characters in some files? So far I have only seen the problem with the character 'c'.

I am sure I am overlooking something simple as these js files work fine without the reverse proxy.

I would be thankful for any ideas.

[connortechnology]

It may be that the c in the code is actually a cyrillic c. We have seen this a few times due to russian contributors. We thought we had them all filtered out, but we will scan again.

[connortechnology]

We did find one cyrillic character, but most were fixed a long time ago. Please make sure you are up to date.

[gutow]

Thank you. I will try an update. Has this been pushed to the ubuntu ppa for stable (1.38)?

[gutow]

The answer appears to be that the ppa has not been updated since I opened this discussion. Thus, I am as up-to-date as I can be without installing from the git repo. I may not get to that for a while. I will report back when I get a version newer than 1.38.3 installed.

[gutow]

I see that the 'c' I have been having trouble with was fixed before the 1.38.3 release. Is it possible that minified versions of the js, where not updated?