This is probably working as intended -- Chromium infers clock skew between the server and the client when calculating cookie expiration (https://chromiumcodereview.appspot.com/11339032).

So if you are setting a cookie that is expired with respect to server time, it won't matter that you have adjusted your system clock backwards, it will still be considered expired.

Do you have a concrete example of the values being set, and the server time being returned in the HTTP response?

But other browsers support this handling. 

Thank you for providing more feedback. Adding requester "eroman@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Other browsers supporting it doesn't necessarily make that the correct behavior. Please provide an example and I can review. Adjusting for time skew fixes a different class of issues. And if your clock is too far off even HTTPS will stop working.

Adding the label Needs-feedback as per # 4

Too far means how much time. 

I have checked one site where changes the system date to 1st november 2015 then page is loaded but google-analytics library not loaded.

On this website there are two https calls which is working fine on changing the date to 1/11/2015 but https://www.google-analytics.com/analytics.js library not loaded.

Please comment on this.  

Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

RE comment #6 -- analytics.js is served with a certificate that is not valid before April 27, 2016, so it will not work if your date is Nov 2015.

But my https call are working fine even if system date is set to past date.

As per your old comment, these should be stop working.

@riyazpanarwala: I don't follow. Are you saying that you *can* load https://www.google-analytics.com/analytics.js when your clock is set to 2015? You shouldn't be able to, as we expect that to fail with ERR_CERT_DATE_INVALID.

Either way the original bug is still a won't fix as noticing clock skew between client and server when setting cookies is intentional. Do you have a use-case or example for why you think that should work?