Tickets :: Comment on [#12970] Don't override sticky OPTIONS values with default values.

* Your Email Address
* Spam protection	Enter the letters below: . . .\ /.___..__. \| \|\ \| >< \| [__] \|___\| \\|/ \ \| \| \|
Comment	>> There is no such thing as "being defined" in EAS. The only time we >> look at previously sent values for a collection's OPTIONS is when the >> client issues a PARTIAL SYNC. Then we load the ENTIRE previously >> requested collection data. If a SYNC request sends an OPTIONS >> structure, it MUST contain the MIMESUPPORT field, or it defaults to 0. > > Ok, but what I mean is that MIMESUPPORT is defined when the SYNC > > OPTIONS is being sent. It only happens when settings things up. > Afterwards, there is never another SYNC > OPTIONS being sent. > > And according to 2.2.3.115.5, these options have to be kept in the > database and re-used across requests: > "The server preserves the Options block across requests, using a > concept referred to as "sticky options". If the Options block is not > included in a request, the previous Options block is used. " > > > Regarding the patch, it's half working. > > For the encrypted message, same as before in the logs, but the device > now knows it's an encrypted message, but still receives it as HTML > and can't decrypt it. > > For signed messages, there are now extra steps. > First the message is the usual HTML one with no MIMESUPPORT in > getMessage, but then it triggers an itemoperation which includes > MIMESUPPORT. >
Attachment
Watch this ticket