4 ms·
This site is only using mm/dd/yyyy for the generator input, the standard itself is not. The actual format in the security.txt file looks like: Expires: Tue, 16
by omni 6y ago
This site is only using mm/dd/yyyy for the generator input, the standard itself is not. The actual format in the security.txt file looks like:
Expires: Tue, 16 Mar 2021 05:09 -0400
Maybe slow down, read the spec, and proofread your comment for obvious errors before trying to troll for no reason.
- brimstedt 6y agoI still think iso standard would be better: https://github.com/securitytxt/securitytxt.org/issues/72 https://github.com/securitytxt/securitytxt.org/issues/72
- BrandoElFollito 6y ago> This site is only using mm/dd/yyyy for the generator input If this is intended to be some kind of standard, it should follow other standards. I understand that this is "only" in the generator, but why even there?
- madeofpalk 6y agoIt’s just using the standard date input. Formatting of the input UI will depend on browser, OS, and locale of the users device.
- BrandoElFollito 6y agoAhhhh! Thanks for the update - I stand corrected. I am French and my Chrome is set to US English. I just opened a FF session, switched to French and the input is dd/mm/yyyy.
- codefined 6y agoHas the generator been updated? For me (UK) it's localised to dd/mm/yyyy, as I would expect in my region. I like that the spec uses a universal and unambiguous format. I especially like that this generator is localised to my region though.
- BrandoElFollito 6y agoNo, as @madeofpalk mentioned in response to my comment, it is using the standard date input. What you actually see depends on the locale of the browser (I see mm/dd/yyy in Chrome set to US English, and dd/mm/yyyy on FF set to French)