A very strange behaviour occurs using particular date 24/09/1967, this is the date when change in Europe/Italy from +1 to +2 "winter time" . I have a service that retrieve from backend a timestamp that represent 24/09/1967 date in this format -71715600000. AngularJs material mdp-date-picker show correctly 24/09/1967. If I inspect -71715600000 value in https://www.epochconverter.com/ I have this results. Epoch converter with -71715600000
Than from Frontend without any modification I save my data, and my angular model contains a new timestamp: -71719200000 Epoch converter with -71719200000
I notice that from windows machine and chrome browser will be put +2 hours in timezone. If I do the same things on a linux chrome browser (linux are configured with same timezone of windows +2), timestamp saved from my frontend are always +1. my question is:
- How is It possible that epoch basing only on -71715600000 timestamp can understand that timezone are +1 and after on the same browser It said that -71719200000 is +2?
- Why Chrome windows add +2 and chrome linux +1 If I have same timezone configured?
- If I save my date 24/09/1967 from FE Windows Chrome and save to a BE store procedure fiscal code check there is an error because store procedure need timezone +1. If I save the same date from Linux It works!!
I have no idea... :-( Thanks in advance for all your response.