Environment
Novell Access Manager 3.1.2 IR3a
Novell Data Synchronizer Connector for Mobility
Novell Data Synchronizer Connector for Mobility
Situation
Purpose:
Protect Novell Data Synchronizer server behind Novell Access Manager
Symptoms:
While some devices works properly while connected to Data Synchronizer server through Access Manager, Nokia devices E71 and E52 doesn't successfully complete the synchronization.
Working without Access Manager, having the Nokia devices connected directly to Data Synchronizer server, everything works as expected.
Protect Novell Data Synchronizer server behind Novell Access Manager
Symptoms:
While some devices works properly while connected to Data Synchronizer server through Access Manager, Nokia devices E71 and E52 doesn't successfully complete the synchronization.
Working without Access Manager, having the Nokia devices connected directly to Data Synchronizer server, everything works as expected.
Resolution
The issue has been fixed in Novell Access Manager 3.2
In case you experience issues while connecting Nokia E71 and/or E52 to Novell Data Synchronizer server through Novell Access Manager, please open a Service Request with Novell Technical Support and point to this TID.
In case you experience issues while connecting Nokia E71 and/or E52 to Novell Data Synchronizer server through Novell Access Manager, please open a Service Request with Novell Technical Support and point to this TID.
Additional Information
Even if this issue was originally found while using Nokia E71 and
E52, this doesn't imply that these are the only affected mobile
devices.
Based on the current findings, the issue seems to be related to mobile devices that sends "Expect: 100-continue" in the header when executing the POST to request the synchronization to Novell Data Synchronizer server. When this happens, the Data Synchronizer replies with an "HTTP/1.1 100" response, and the access gateway use the "content-type:text/plain" of this response also when forwarding the subsequent "HTTP/1.1 200 OK", that contains the real data, to the client on the mobile device; this content-type mismatch seems to be the root cause of the problem here.
Based on the current findings, the issue seems to be related to mobile devices that sends "Expect: 100-continue" in the header when executing the POST to request the synchronization to Novell Data Synchronizer server. When this happens, the Data Synchronizer replies with an "HTTP/1.1 100" response, and the access gateway use the "content-type:text/plain" of this response also when forwarding the subsequent "HTTP/1.1 200 OK", that contains the real data, to the client on the mobile device; this content-type mismatch seems to be the root cause of the problem here.