-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 To whom it may concern,
On 3/11/13 11:17 AM, getridofthespam wrote: > Google didn't give any relevant info so I try here. > > I traced a tomcat request and noticed there where two different > date formats in the last-modified header: 2012-12-13T09:52:02Z and > Mon, 07 Jan 2013 21:49:08 GMT > > What determines the format and where do the differences come from? RFC 2616 (HTTP)[1] does not directly reference RFC 2822 (Internet Message Format), but that's the format that's being used -- covered in section 3.3 [2]. That's where the format that begins with the day-of-week. I'm surprised that Tomcat ever emits anything that looks like yyyyMMddTHHmmssZZ -- that's ISO 8601 date formats. Since ISO 8601 predates HTTP, I'm not sure why that wasn't chosen. But HTTP has some old crap that should have never been put into the protocol from day one, so why not an insane date format specification? - -chris [1] http://tools.ietf.org/html/rfc2616#section-13.3.1 [2] http://tools.ietf.org/html/rfc2822#section-3.3 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlE+Qm4ACgkQ9CaO5/Lv0PBWZgCgtPmB6J8EVB6nZgOv57EmEvvX ScsAniX9s6fDJNmHFAbbfDuDClo7T1X5 =VS3F -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
