IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
Regarding the default Google Scheduler headers sent in HTT targets, Google documentation refers: “X-CloudScheduler-ScheduleTime: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule time in RFC3339 UTC "Zulu" format.” [1]
But actually when accessed this header the timestamp sent by Google Cloud Scheduler was sent with timezone -07:00 (USA timezone). Because of this we have to do extra steps to convert timezone from -07:00 into 00:00 (UTC)
This should be fixed and timestamp sent in UTC or new feature could be added to send this timestamp in Cloud Scheduler region timezone, not USA.


What you expected to happen:
X-CloudScheduler-ScheduleTime contains timstamp with timezone in UTC or related to Scheduler region

Steps to reproduce:
Read X-CloudScheduler-ScheduleTime header sent by Cloud Scheduler through HTTP

Other information (workarounds you have tried, documentation consulted, etc):
[1]: https://cloud.google.com/scheduler/docs/reference/rpc/google.cloud.scheduler.v1#httpmethod