Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 57842 invoked by uid 500); 28 Mar 2003 17:36:04 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 57766 invoked from network); 28 Mar 2003 17:36:04 -0000 Date: Fri, 28 Mar 2003 09:35:20 -0800 From: Justin Erenkrantz To: Dmitri Tikhonov , dev@apr.apache.org Subject: Re: Date-parsing routines -- uncovered case. Message-ID: <2147483647.1048844120@localhost> In-Reply-To: <20030327232037.GB8071@netilla.com> References: <20030327232037.GB8071@netilla.com> X-Mailer: Mulberry/3.0.3 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=-2.5 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES version=2.50-cvs X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --On Thursday, March 27, 2003 6:20 PM -0500 Dmitri Tikhonov wrote: > There are two date-parsing routines in apr-util: > > apr_date_parse_rfc > apr_date_parse_http > > However, I encountered one date format that neither of these functions > can parse: > > Sat, 26-Mar-2005 23:14:33 GMT > > It is an expire for cookies generated by InfoPop's forum product. You can > see it in action here: > > http://community.infopop.net/2/OpenTopic > > While this date string does not adhere to standards, I think we should have > a function that would be able to parse it. Feel free to submit a patch that adds it to apr_date_parse_rfc. -- justin