Feedparser und Seriengrenzen

ICS feed reader

ParseFeed recognizes RSS 2.0 event feeds, jCal (RFC 7265), xCal (RFC 6321), a bounded subset of Schema.org Event JSON-LD, and JSON and CSV feeds by content. The custom JSON/CSV and Schema.org formats contain individual events with stable IDs; they do not express recurrence. jCal and xCal share the supported iCalendar recurrence subset. The complete schema and examples are documented in Terminformate. Malformed or ambiguous entries reject the whole refresh, including entries outside the requested window. Empty lists are valid.

Parse consumes a complete UTF-8 VCALENDAR 2.0 and expands event occurrences that overlap the requested window. It supports UTC and IANA TZID timestamps, floating timestamps using X-WR-TIMEZONE (default Europe/Berlin), all-day exclusive ends, DTEND/DURATION, folded lines and escaped text.

Recurrence support: DAILY, WEEKLY, MONTHLY and YEARLY; INTERVAL, COUNT, UNTIL, WKST, BYDAY (including ordinal weekdays), BYMONTH, BYMONTHDAY and BYSETPOS. EXDATE/RDATE and RECURRENCE-ID overrides are applied. Original recurrence IDs form stable keys for moved/cancelled instances. ABGESAGT: in the title marks an occurrence cancelled. Missing items in a feed are not cancellation evidence.

Unsupported recurrence features (including sub-daily frequencies, BYHOUR, BYMINUTE, BYSECOND, BYWEEKNO, BYYEARDAY, EXRULE, RANGE=THISANDFUTURE and period RDATE values) cause the entire refresh to fail. Custom VTIMEZONE definitions cannot override the embedded IANA database; an unknown TZID fails. Duplicate masters/overrides and malformed entries fail rather than publish a partial feed.

Bounds: 8 MiB source, 128 KiB unfolded lines, 20,000 components, 50,000 output occurrences, one million recurrence date evaluations, six-year maximum query window and one-year event duration. Advanced exports may be rejected with a visible stale status.

Client.Fetch accepts publicly reachable HTTPS and webcal:// feed addresses; webcal is fetched over HTTPS. A filename extension is not required, and query parameters and ports are allowed. URL userinfo and fragments are rejected. Up to five HTTPS redirects are followed; each destination is subject to the same network checks and no referrer is sent. The production transport checks DNS answers, rejects local and special-purpose IPs and dials a checked IP directly; it does not use HTTP proxies. Requests have a 25-second timeout and a response size bound. Errors never include the secret address. A caller can inject Client.HTTP with a test RoundTripper; production should use NewClient().

Tests cover Berlin DST, all-day and nominal DURATION day units, monthly/yearly selection, COUNT/UNTIL, EXDATE/RDATE, moved/cancelled overrides, folded text, quoted attendee parameters, rejection of unsupported/partial feeds and protected HTTPS feed fetches. No live private calendar was accessed.

Reference: RFC 5545, sections 3.1, 3.3.5–3.3.6, 3.3.10 and 3.8.5. https://www.rfc-editor.org/rfc/rfc5545