Hi All,
by accident when testing with the current chrome beta I discovered that with any browser based on chromium 137 onwards zimbra web client fails to load.
I double checked with multiple zimbra installations (10.1.6 NE, 10.1.6 FOSS build, 8.8.15) and always the loading of the webclient after login gets stuck with /service/soap/BatchRequest returning a 500 with a soap reason "unknown document: BatchRequest," I encountered it with Chrome 137.0.7151.15-1, Chromium 137.0.7151.6 and Edge 137.0.3296.4-1.
Using multiple other browsers (Firefox, Chrome / Chromium 136) everything works just as expected.
Did anybody else encounter the same issue? Given that according to https://chromiumdash.appspot.com/schedule Chrome 137 is supposed to be released as stable in 2 weeks, this seems like it could be an issue ...
Best regards,
Stefan
by accident when testing with the current chrome beta I discovered that with any browser based on chromium 137 onwards zimbra web client fails to load.
I double checked with multiple zimbra installations (10.1.6 NE, 10.1.6 FOSS build, 8.8.15) and always the loading of the webclient after login gets stuck with /service/soap/BatchRequest returning a 500 with a soap reason "unknown document: BatchRequest," I encountered it with Chrome 137.0.7151.15-1, Chromium 137.0.7151.6 and Edge 137.0.3296.4-1.
Using multiple other browsers (Firefox, Chrome / Chromium 136) everything works just as expected.
Did anybody else encounter the same issue? Given that according to https://chromiumdash.appspot.com/schedule Chrome 137 is supposed to be released as stable in 2 weeks, this seems like it could be an issue ...
Best regards,
Stefan
Statistics: Posted by sensor — Mon May 12, 2025 7:15 am