DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16521>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16521 caches MUST treat invalid Expires values as in the past ------- Additional Comments From [EMAIL PROTECTED] 2003-07-09 06:36 ------- This patch (attachement ID 7186)is to fix the date followed by junk, in all RFC 850, RFC 1123 and Asctime formats. Do we need to handle the condition where the Date is not represented in GMT or no time zone is specified? (Example: "Sun, 06 Nov 1994 08:49:37 ") RFC 2616, 3.3.1 says: All HTTP date/time stamps MUST be represented in GMT, without exception. HTTP-date is case sensitive and MUST NOT include additional LWS beyond that specifically included as SP in the grammar. Note: Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications, as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
