> Begin forwarded message:
>
> From: Dominik Chyziak <[email protected]>
> Subject: Re: [FEATURE] Support Time-Zone header in REST API
> Date: April 8, 2026 at 4:55:38 AM GMT+8
> To: Haonan Hou <[email protected]>
>
> Hi everyone,
>
> Thank you, Haonan, for the review.
>
> This change introduces support for a Time-Zone HTTP header in the v1 and v2
> REST APIs, allowing clients to specify the session time zone. The header
> accepts any value compatible with Java's java.time.ZoneId.
>
> A client in Europe wants to query for data recorded up to 12:00 PM local
> time. They can send the following request:
>
> curl -X POST http://127.0.0.1:18080/rest/v1/query \
> -H "Authorization: Basic cm9vdDpyb290" \
> -H "Content-Type: application/json" \
> -H "Time-Zone: Europe/Warsaw" \
> -d '{"sql":"SELECT temperature FROM root.factory.sensor1 WHERE time <=
> 2026-04-10T12:00:00"}'
>
> If the header is omitted, the session will use the server's default time
> zone. Providing an invalid value will result in a 400 Bad Request.
>
> Best regards,
> Dominik Chyziak
>
>
> wt., 7 kwi 2026 o 05:37 Haonan Hou <[email protected]
> <mailto:[email protected]>> napisał(a):
>> Hi Dominik,
>>
>> Thanks for your contribution. I will review this PR again.
>> Would you like to share the new usage of the timezone setting in REST API in
>> this mail list?
>>
>> Best regards,
>> Haonan Hou
>>
>> > On Apr 5, 2026, at 5:38 PM, Dominik Chyziak <[email protected]
>> > <mailto:[email protected]>> wrote:
>> >
>> > Hi everyone,
>> >
>> > I have implemented support for the Time-Zone header in the REST API. This
>> > allows users to specify the session time zone directly via HTTP headers.
>> >
>> > The PR includes integration tests and updated examples. You can find the
>> > details here:
>> > https://github.com/apache/iotdb/pull/17387
>> >
>> > Best regards,
>> > Dominik Chyziak
>>
