[horde] problem ActiveSync Android Event with end date

[Michael J Rubinsky]

Quoting Steffen <skhorde at smail.inf.fh-bonn-rhein-sieg.de>:

> On Fri, 31 Jan 2014, Michael J Rubinsky wrote:
>
>> Quoting Steffen <skhorde at smail.inf.fh-bonn-rhein-sieg.de>:
>>
>>> On Fri, 10 Jan 2014, Steffen wrote:
>
>>> 12:03 one event repeated each 4th week end on 28th March
>>
>> ^^^ This event is NEVER sent to the server, at least not in the log  
>> you posted.
>
> OK, thanks for checking the logs.
>
>>> Most interessting is that the time stamp gets 1 hour back ??? From 12:04
>>> to 11:04. It's another PID. During that phase, no Calendar entries in
>>> the log. I also had log entries another time with a line:
>>> Skipping @Calendar@ because it is not PINGable.
>>>
>>> Then there is a jump in the hour again with the same PID at the time
>>> I remove the repeated event:
>>> 2014-01-30T11:08:01+00:00 DEBUG: [1671] I       </Data>
>>> 2014-01-30T11:08:01+00:00 INFO: [1671]
>>> Horde_Core_ActiveSync_Driver::changeMessage(@Calendar@,  ...)
>>> 2014-01-30T12:08:01+01:00 INFO: [1671] Updating state during change
>>> 2014-01-30T12:08:01+01:00 DEBUG: [1671] I      </Add>
>>>
>>> And with the "12" hour logs, the "Calendar" stuff appears again.
>>>
>>> The log is attached
>>
>> I have no idea what is going on. Your synclog also seems to  
>> indicate your client is issuing multiple, identical requests. Given  
>> the fact that the event in question is not even sent to the server  
>> from the client, this seems like a client bug.
>
> Hmm, I will try this with other setups.
>
> Do you have an idea, why the log time stamp warps one hour back into  
> the past and back into current again? Is Horde switching to UTC  
> maybe? The 1 hour is the difference of the local server time to UTC.

No idea, it's not the ActiveSync library doing this. The log time  
comes directly from PHP's date() function, so for some reason you have  
two different PHP processes using two different timezones. You will  
have to track this down yourself, as I cannot reproduce this.

> Is it possible that the time difference break the acceptance of some  
> request / response?

Doubtful. Your log shows you are using modification sequences anyway,  
not timestamps, for the syncstamps.

> I mean, several SYNC implementations add sanity checking that a SYNC  
> message is in a defined time frame. Maybe Horde tags responses with  
> a timestamp, which is one hour too old?

No. There is no "timestamp tag" like that sent in ActiveSync. We  
perform a multitude of sanity checks to be sure there are no race  
conditions set up from multiple requests by the same client, but there  
is no requirement in ActiveSync that a SYNC message occur withing a  
certain timeframe.

-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5849 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/horde/attachments/20140205/bd706ed5/attachment.bin>