[sync] Horde EAS 14.0: HTTP 500 error if calendar add item requests contains NativeBodyType

Michael J Rubinsky mrubinsk at horde.org
Wed Jan 24 14:17:59 UTC 2018


Yeah, understood. Unfortunately, that's also a lot more work ;)

--
Mike
Sent from mobile
________________________________
From: John Bieling <john.bieling at gmx.de>
Sent: Wednesday, January 24, 2018 2:55 AM
To: mrubinsk at horde.org
Subject: Re: [sync] Horde EAS 14.0: HTTP 500 error if calendar add  
item requests contains NativeBodyType

> For me, this has no priority, I just wanted to understand, where the  
> error comes from and inform you about my finding.
>
> Much greater value would have the issue with the changing UIDs.
>
> Thanks
> John
>
>
>
> Am 24.01.18 um 06:44 schrieb Michael J Rubinsky
>
>> Quoting John Bieling <john.bieling at gmx.de>:
>>
>> > Hi,
>> >
>> > its me again. I have run into a strange error: If I send a request
>> > to horde, to add a calendar event, that includes "NativeBodyType", I
>> > get back a HTTP 500 error. I could be doing something wrong, but as
>> > it is not failing with Mirosoft EAS and zpush, I wanted to post this
>> > here.
>> >
>> > It does not matter, if I add the NativeBodyType before or after the
>> > the Body tag.
>>
>> Yeah, sorry for the delay in responding.  It doesn't look like I ever
>> implemented this tag with respect to calendar items, just Mail items.
>> I've put it on my todo list and will look at it shortly.
>>
>>
>> >
>> > This is such a request:
>> >
>> > <?xml version="1.0"?>
>> > <Sync xmlns='AirSync'>
>> > <Collections>
>> > <Collection>
>> > <SyncKey>{5a4ea61e-cbc4-4ba0-8b88-0681b0098baf}2</SyncKey>
>> > <CollectionId>Aadfc2207</CollectionId>
>> > <Commands>
>> > <Add>
>> > <ClientId>1ac68dd6-b72a-4166-9a67-5d497ec9be6b</ClientId>
>> > <ApplicationData>
>> > <UID xmlns='Calendar'>1ac68dd6-b72a-4166-9a67-5d497ec9be6b</UID>
>> > <TimeZone
>> >  
>> xmlns='Calendar'>xP///ygARwBNAFQAKwAwADEAOgAwADAAKQAgAEUAdQByAG8AcABlAC8AQgBlAHIAbABpAG4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgARwBNAFQAKwAwADEAOgAwADAAKQAgAEUAdQByAG8AcABlAC8AQgBlAHIAbABpAG4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</TimeZone>
>> > <StartTime xmlns='Calendar'>20180116T220000Z</StartTime>
>> > <EndTime xmlns='Calendar'>20180116T230000Z</EndTime>
>> > <DtStamp xmlns='Calendar'>20180104T221008Z</DtStamp>
>> > <BusyStatus xmlns='Calendar'>2</BusyStatus>
>> > <Sensitivity xmlns='Calendar'>1</Sensitivity>
>> > <AllDayEvent xmlns='Calendar'>0</AllDayEvent>
>> > <Subject xmlns='Calendar'>asdsa</Subject>
>> > <Location xmlns='Calendar'>sadasd</Location>
>> > <Categories xmlns='Calendar'/>
>> > <Attendees xmlns='Calendar'/>
>> > <NativeBodyType xmlns='AirSyncBase'>3</NativeBodyType>
>> > <Body xmlns='AirSyncBase'>
>> > <Type xmlns='AirSyncBase'>1</Type>
>> > <EstimatedDataSize xmlns='AirSyncBase'>6</EstimatedDataSize>
>> > <Data xmlns='AirSyncBase'>asdasd</Data>
>> > </Body>
>> > </ApplicationData>
>> > </Add>
>> > </Commands>
>> > </Collection>
>> > </Collections>
>> > </Sync>
>> >
>> > And this the actually send WBXML
>> >
>> > 3 1 6a 0 45 5c 4f 4b 3 7b 35 61 34 65 61 36 31 65 2d 63 62 63 34 2d
>> > 34 62 61 30 2d 38 62 38 38 2d 30 36 38 31 62 30 30 39 38 62 61 66 7d
>> > 32 0 1 52 3 41 61 64 66 63 32 32 30 37 0 1 56 47 4c 3 31 61 63 36 38
>> > 64 64 36 2d 62 37 32 61 2d 34 31 36 36 2d 39 61 36 37 2d 35 64 34 39
>> > 37 65 63 39 62 65 36 62 0 1 5d 0 4 68 3 31 61 63 36 38 64 64 36 2d
>> > 62 37 32 61 2d 34 31 36 36 2d 39 61 36 37 2d 35 64 34 39 37 65 63 39
>> > 62 65 36 62 0 1 45 3 78 50 2f 2f 2f 79 67 41 52 77 42 4e 41 46 51 41
>> > 4b 77 41 77 41 44 45 41 4f 67 41 77 41 44 41 41 4b 51 41 67 41 45 55
>> > 41 64 51 42 79 41 47 38 41 63 41 42 6c 41 43 38 41 51 67 42 6c 41 48
>> > 49 41 62 41 42 70 41 47 34 41 41 41 41 41 41 41 41 41 41 41 41 41 41
>> > 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41
>> > 41 41 41 41 41 41 41 41 41 43 67 41 52 77 42 4e 41 46 51 41 4b 77 41
>> > 77 41 44 45 41 4f 67 41 77 41 44 41 41 4b 51 41 67 41 45 55 41 64 51
>> > 42 79 41 47 38 41 63 41 42 6c 41 43 38 41 51 67 42 6c 41 48 49 41 62
>> > 41 42 70 41 47 34 41 41 41 41 41 41
>> >  41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41
>> > 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 3d 3d 0 1
>> > 67 3 32 30 31 38 30 31 31 36 54 32 32 30 30 30 30 5a 0 1 52 3 32 30
>> > 31 38 30 31 31 36 54 32 33 30 30 30 30 5a 0 1 51 3 32 30 31 38 30 31
>> > 30 34 54 32 32 31 30 30 38 5a 0 1 4d 3 32 0 1 65 3 31 0 1 46 3 30 0
>> > 1 66 3 61 73 64 73 61 0 1 57 3 73 61 64 61 73 64 0 1 e 7 0 11 56 3
>> > 33 0 1 4a 46 3 31 0 1 4c 3 36 0 1 4b 3 61 73 64 61 73 64 0 1 1 0 4 0
>> > 0 1 1 1 1 1 1
>> >
>> > Thanks for your help
>> > John
>> >
>> >
>> >
>> > --
>> > sync mailing list
>> > Frequently Asked Questions: http://wiki.horde.org/FAQ
>> > To unsubscribe, mail: sync-unsubscribe at lists.horde.org
>>
>>
>>
>> --
>> mike
>> The Horde Project
>> http://www.horde.org
>> https://www.facebook.com/hordeproject
>> https://www.twitter.com/hordeproject
>> --
>> sync mailing list
>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>> To unsubscribe, mail: sync-unsubscribe at lists.horde.org
>




More information about the sync mailing list