HTTP OPTIONS request Content-Type

There is a problem with the formulation of the OPTIONS header used when syncing with a CalDAV/CardDAV server. The OPTIONS header contains the following option:

Content-Type: text/xml; charset=utf-8

However, the Content-Length is 0, i.e. there is no actual xml included.

The Content-Type for OPTIONS requests should changed to text/basic OR some xml should be included.

This issue causes synchronization of calendar tree with DAViCal 1.0.2 to fail since it returns HTTP 400 Bad Request with reason .

Best Regards,

Fixed in our private builds. The fix will be present in next application update or you can contact me directly at [email protected] to get early access.

After last update I have bad encoding of titles in inbox emails:
Potvrzen=?UTF-8?Q?=C3=AD objedn=C3=A1vky prodlou=C5=BEen=C3=AD dom=C3=A9ny

Before update everything was fine:
Upozornění na expiraci domény

Now I have emclient 5.0.18661.0

Please send one of the problematic messages saved as .eml to my colleague Navara at [email protected]. Include a reference to this topic so he can get back to you and post here a solution. Thank you.