6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/4/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#12970] Don't override sticky OPTIONS values with default values.
*
Your Email Address
*
Spam protection
Enter the letters below:
.__..__.. .. ,.___ [__]| || | \./ [__ | ||__\|/\| | [___
Comment
> >> 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. " > > Correct, and we already do that. > > I was misunderstanding what was happening on your end. I thought the > client WAS sending an OPTIONS request, but was just not including the > MIMESUPPORT. We fill in any missing values in > Horde_ActiveSync_SyncCache::validateCollectionsFromCache() > > Maybe what is happening is that at some point after the initial sync, > the client IS sending an OPTIONS request either without the > MIMESUPPORT or with it set to 0. This then becomes the cached value > of the OPTIONS to be used when it is omitted. > > You can verify that the MIMESUPPORT value is being cached by looking > in the table horde_activesync_cache. >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers