tracker issue : CF-3040433

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 80734:(Watson Migration Closure)Summary: parseDateTime() should work for RFC-822-formatted datesThe standard format for dates on internet is defined by RFC-822 (http://tools

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 11/19/2009

Components: Language, Functions

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 / 289002

Priority/Frequency: Minor / Unknown

Locale/System: English / Platforms All

Vote Count: 0

Problem:

Summary: parseDateTime() should work for RFC-822-formatted datesThe standard format for dates on internet is defined by RFC-822 (http://tools.ietf.org/html/rfc822#section-5).CF will not parse dates in this format (eg: "13 Nov 2009 20:51:47 GMT"); it seems to fail because of the TZ.lsParseDateTime() likewise fails.I've flagged this as a "benign bug" because that's the closest caegorisation, but it's also a stupid category name.  It's a bug which causes code to fail: it's not benign.  But there is a way to work around it.-- Adam
Method:


Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3040433

External Customer Info:
External Company:  
External Customer Name: Adam Cameron
External Customer Email: 17EB1A7649DA54C7992015A9
External Test Config: 11/19/2009

Attachments:

Comments:

This actually seems to have been fixed along the way. You might want to update it accordingly (with the correct fix version, etc)
Comment by External U.
22521 | October 28, 2014 05:29:19 AM GMT