6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
7/29/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
>>> That doesn't matter. It's supposed to be set for each >>> fetch/sync/itemoperation to tell the server the client can accept the >>> MIME blob. If it's missing, it's assumed to be zero. See MS-ASCMD >>> section 2.2.3.100.3. >> >> I don't think so. 2.2.3.100.3 says that it has to be part of every >> Sync>Options request and it is when the collection is being defined. > > 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.
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