So I guess that i can live with someone making the decision to format the date time as European time.
But I am just wanting to know who had the ingenious idea to zero index the months so that January is month 0 and December is month 11....
Not sure if someone was trying to be funny or pretentious.
Debugging code today December 7, 2018 at 17:21 and here is what I see in the time field.
Just wanting to chat with the genius that thought this would be the best idea.
This is simply never used and not processed. It is send that is all.
In terms of timestamp:
I totally feel you. Granted, this was implemented well over a decade ago. I'm pretty sure it even predates G code...
Thankfully it's automatically collected and not surfaced anywhere important. The Experience Cloud Debugger extension doesn't show it anywhere in an image request since it's just one of those things that just works behind the scenes.
But still - I do share a similar opinion. When I first found out about image request query string dates being 0 for January, I could not figure out for the life of me why they did that.
I believe it is just a result of coding standards at the time. I think the code related to query param t= is as follow
As you can see they using date and I found a related topic here:
Wow, thanks Alexis! In that thread, it looks like the JS's date was directly ported from Java 1.0, which led to this question: Why is January month 0 in Java Calendar? - Stack Overflow
The first answers mentions that's it's simply a mess, but the second answer provides some pretty solid logic in that it's a lot easier to calculate month differences using the % operator.