On Wednesday 16 March 2005 10:19 pm, Joe Schaefer wrote:
> > What should the manpage say? something like the following?
> > The function assumes GMT, regardless of the used timezone,
> > according to RFC 2616 Section 3.3 requires.
> No need to mention the RFC; how about this?
The current doc says:
# parse RFC822-complient date string
Which it doesn't (as RFC822 includes multiple timezones). In fact none of the
RFCs listed are 2616. Whilst parse_http does seem like it should follow
RFC2616, is thare a reason parse_rfc should too?
> APR::Date::parse_http is a perl wrapper for the
> apr_date_parse_http() function provided by libaprutil.
> Please check your libaprutil documentation for a complete
> list of supported formats and restrictions (in particular,
> this function assumes GMT, regardless of the used timezone).
How about simply correcting the parse_http docs from:
The date string can be in one of the following formats:
to:
The date string can be in one of the following formats (as per RFC2616):
That way anyone interested can look up the correct RFC if they want the gory
details.
I'm not sure about parse_rfc as I'm not sure what it's actually supposed to be
able to parse.
