This is fixed in SPLICE v1.2.
Could you please send me an email ? I would like to submit you a patch for testing.
Thanks.
Thanks for your feedback.
Can you be more specific on the use case or need?
What's missing/blocker if you don't have this feature?
Thanks for the answer.
We are developing TAXII Poll Service. Both the service and SPLUNK with SPLICE are running in the +01:00 timezone.
When SPLICE sends a Taxii Poll request, it always sends Exclusive_Begin_Timestamp with timezone being +00:00.
Our service then handles the Poll request and represents the Exclusive_Begin_Timestamp as being one hour in the future.
So all the requests return incorrect data because of this time shift.
A first version of our TAXII server is about to be launched soon, but no clients using SPLICE can use it unless this timezone problem is fixed so it's a showstopper for us at the moment.
Providing the correct timezone in the request would solve our problem. (There are TODO's to add TZ support in the SPLICE souce code.)