Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 521546 - [news] Feed parser should be resilient to malformed <pubDate> values
Summary: [news] Feed parser should be resilient to malformed <pubDate> values
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Recommenders (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Andreas Sewe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-29 11:26 EDT by Andreas Sewe CLA
Modified: 2019-07-24 14:35 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Sewe CLA 2017-08-29 11:26:09 EDT 
The feed parser we use (based on Mylyn) is very strict and accepts only (RFC 822 dates [1] for <pubDate>:

  Wed, 02 Oct 2002 08:00:00 EST
  Wed, 02 Oct 2002 15:00:00 +0200

Unfortunately, in-the-wild feeds like [2] contain may malformed <pubDate> values:

  Tue, 18 Sept 2007 09:00:00 EST
  Wed, Feb 03, 2010 14:34:37 EST
  Fri, 04 Jun 2010 13:55 EST
  Wed, Feb 23, 2011 09:40:00 AM EST
  Tue, 1 Mar 2011 12:25:00 PM EST
  August 22, 2017 9:00:00 am EST

Our feed parser should hence be more resilient.

[1] <https://validator.w3.org/feed/docs/error/InvalidRFC2822Date.html>
[2] <http://www.eclipse.org/home/eclipsenews.rss>
Comment 1 Eclipse Genie CLA 2017-08-29 11:28:49 EDT 
New Gerrit change created: https://git.eclipse.org/r/103877