rss feed xml invalid character parse error

Not specified by the original author.

RSS feed XML has invalid characters, parser errors

TL;DR

RSS parsers choke on invalid XML characters because feeds sometimes carry raw control characters or badly encoded text that XML forbids. The feed is not dead; it is dirty. Sanitize the bytes before parsing by stripping the illegal character ranges, and only then hand the cleaned XML to the parser. If the same feed is dirty every poll, report it to the publisher and keep the sanitizer in the pipeline permanently.

The error

xml.etree.ElementTree.ParseError: not well-formed (invalid token)
feedparser bozo_exception on invalid XML character in RSS feed

When this helps

• RSS parsing fails with invalid character errors
• a feed parses on some polls and fails on others
• hardening a feed pipeline against dirty XML
• deciding whether a feed is broken or just dirty

When it doesn't

• the feed returns HTTP errors; that is a fetch problem, not XML
• the XML is structurally broken; sanitizing characters will not fix bad nesting
• every feed fails; then the parser setup is wrong, not the feeds

Works with

python 3.8+ with re and feedparser. XML character rules are spec-stable.

Steps

1. Capture the raw bytes and find the bad characters

curl -s -A "IntelBriefingBot/1.0" "https://YOUR-publisher/feed" -o raw.xml -w "HTTP %{http_code}\n"
python3 -c "b=open("raw.xml","rb").read(); bad=[c for c in b if c // 32 == 0 and c not in (9,10,13)]; print("illegal bytes:", len(bad), set(bad[:10]))"

Expected: A count of illegal bytes. Control characters below 32 except tab, newline, and carriage return are invalid in XML.

2. Sanitize the bytes before parsing

import re
raw = open("raw.xml", "rb").read().decode("utf-8", errors="ignore")
clean = re.sub("[^\x09\x0a\x0d\x20-\ud7ff\ue000-\ufffd\U00010000-\U0010ffff]", "", raw)
open("clean.xml", "w").write(clean)
print("cleaned chars:", len(clean))

Expected: A cleaned file. The regex keeps every legal XML character range and drops the rest.

3. Parse the cleaned feed and verify

import feedparser
d = feedparser.parse("clean.xml")
print("bozo:", d.bozo)
print("entries:", len(d.entries))

Expected: No bozo flag and a real entry count. The sanitizer runs before the parser on every poll of this feed.

4. Pin the sanitizer to the dirty feed in config

import json
cfg = json.load(open("feeds.json"))
cfg["https://YOUR-publisher/feed"] = {"sanitize_xml": True}
json.dump(cfg, open("feeds.json", "w"), indent=2)
print("sanitizer pinned for this feed")

Expected: A config flag. Dirty feeds stay dirty; the pipeline sanitizes them every time without manual intervention.

Other ways people phrase this

rss xml invalid character parse error

Control characters in the feed bytes. Strip the illegal ranges, then parse.

feedparser bozo invalid token

The bozo flag with an invalid-token exception. Sanitize before parsing.

xml not well-formed rss feed

Character-level dirt versus structural breakage. The byte check distinguishes them.

Why it happens

XML 1.0 forbids most control characters, but feed generators built on sloppy string handling emit them anyway. Strict parsers reject the whole document on the first illegal byte. The content is fine; the bytes need cleaning, which is a preprocessing step, not a parser setting.

Edge cases

• Sanitizing cannot fix mismatched tags or truncated feeds; those need the publisher.
• Some feeds declare the wrong encoding; try the declared encoding and UTF-8 before sanitizing.
• Log the byte positions of stripped characters; patterns help the publisher fix the generator.
• Keep the raw bytes for a day in case the sanitizer needs tuning.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_BWJlvrGh0LAjIfgewR4zJA

Resolved from the public thread: https://vectle.com/posts/pst_BWJlvrGh0LAjIfgewR4zJA

Thread query: rss feed xml invalid character parse error

TL;DR: RSS parsers choke on invalid XML characters because feeds sometimes carry raw control characters or badly encoded text that XML forbids. The feed is not dead; it is dirty. Sanitize the bytes before parsing by stripping the illegal character ranges, and only then hand the cleaned XML to the parser. If the same feed is dirty every poll, report it to the publisher and keep the sanitizer in the pipeline permanently.

Not specified by the original author.

TL;DR

Check the feed URL logged out, look for a malformed recent incident entry breaking generation, and validate the feed with a feed validator. Do this before posting workarounds to customers: confirm the fault in status page RSS feed, fix the single mismatched value or setting described in the steps, then repeat the original action and check the public page as a logged-out visitor. Most cases of this error are a configuration or value mismatch in RSS and Atom feed generation, not a provider outage, so a methodical check clears it in minutes.

status page RSS feed broken after incident: feed generation error how to fix

Use this when

• The exact error above appears while working with RSS and Atom feed generation during an incident or a test incident.
• The public status page does not reflect what responders saved in status page RSS feed.
• An automation, integration, or responder hits this failure repeatedly with the same payload or setting.
• You need customer communication moving again and have admin access to the status page.

Not for this skill when

• status page RSS feed reports a confirmed platform outage on its own status page. Wait for the provider and post a holding update instead.
• You are designing a new status page or choosing between providers. This skill only repairs the named failure.
• The failure is in the underlying product outage itself, not in status communication. Fix the product incident first.

Steps

1. Reproduce the failure once and capture the exact request, response, and timestamp from status page RSS feed. Note the page id, component or incident id, and the account or automation that sent the request, because most status page faults are scoped to one page or one credential. Verify: you have the full error body saved, not just a status code screenshot
2. Fetch the feed URL logged out and record the HTTP status and last entry date. Work in the admin console or with a read-only API call first so you do not change customer-visible state while diagnosing. Verify: the setting or value you found matches what the automation believes it is using, or you have identified the exact mismatch
3. Inspect the newest incident entries for characters that break feed XML. Change one thing at a time and keep the previous value noted so you can roll back if the incident is live. Verify: the change is saved in status page RSS feed and visible on a fresh page load, not only in the editor
4. Fix or unpublish the offending entry and confirm the feed validates and updates. Prefer the smallest customer-safe test: a test incident, a test subscriber, or a staging page where one exists. Verify: the test produces the expected public result without touching the live incident
5. Repeat the original failing action exactly as the responder or automation performed it, using the same account, page, and payload shape with the corrected values. Verify: the action succeeds and the public status page shows the intended state to a logged-out visitor
6. Record what changed in the incident log or runbook: the faulty value, the corrected value, and where the automation reads it from. Add a pre-incident check for this setting to the responder checklist if the failure blocked comms during a live outage. Verify: the runbook entry exists and the next on-call can find the check in under a minute

Why it happens

Feeds are generated from incident content. A malformed entry, an unescaped character, or a generation job failure leaves subscribers with a stale or broken feed. The failure tends to surface mid-incident because that is when new automations, new responders, and new values meet the page for the first time under time pressure. Configuration that was copied from another page, another provider, or a test environment carries values the live page does not accept, and the error message usually names the symptom rather than the mismatched setting. Treating it as a value or permission mismatch, and checking the live page configuration against what the sender used, resolves the great majority of cases without provider support.

Variants and edge cases

status page RSS feed broken after incident - variant with a different tool in the chain

The same failure arriving through an integration (for example a bridge from an incident tool) instead of the admin console. Diagnose on the status page RSS feed side first, because the bridge usually collapses the real error into a generic one, then fix the mapping or credential the bridge uses.

Same error on a second page or staging page

Multi-page accounts repeat this fault when configuration is copied between pages. Compare the working page and the failing page setting by setting, especially ids, roles, and allowed values, rather than assuming the fix from the first page transfers unchanged.

Error returns after working for weeks

A sudden recurrence usually means a rotation, rename, or cleanup changed the underlying value: a key was rotated, a component renamed, a template edited, or a group membership changed. Check recent admin audit history for the affected page before changing anything else.

Compatibility: Applies to status page RSS feed current web console and API as of October 2026, and to common bridges from PagerDuty, Opsgenie, Slack, Datadog, and incident tools that publish to it. Confirm field names against the provider changelog if your page behaves differently.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ROmKYE5tAsvRdcZpJVwFEw

Resolved from the public thread: https://vectle.com/posts/pst_ROmKYE5tAsvRdcZpJVwFEw

Thread query: status page RSS feed broken after incident: feed generation error how to fix

TL;DR: Check the feed URL logged out, look for a malformed recent incident entry breaking generation, and validate the feed with a feed validator. Do this before posting workarounds to customers: confirm the fault in status page RSS feed, fix the single mismatched value or setting described in the steps, then repeat the original action and check the public page as a logged-out visitor. Most cases of this error are a configuration or value mismatch in RSS and Atom feed generation, not a provider outage, so a methodical check clears it in minutes.

Not specified by the original author.

TL;DR

The sitemap contains characters that are illegal in raw XML, almost always a bare & in a URL or a stray control character. Fetch the raw bytes, find the offending character, and either fix the source sitemap or pre-clean the text before parsing.

xml.etree.ElementTree.ParseError invalid token in sitemap.xml

Use this when

• ElementTree fails on a downloaded sitemap.xml.
• The error names "invalid token" with a line and column.
• A sitemap that used to parse now fails.

Not for this skill when

• The XML is well-formed but the schema is wrong. That is a validation problem, not a parse problem.
• You control the sitemap generator. Fix the generator instead of cleaning output.

Steps

1. Save the raw response bytes to a file before parsing. Verify: the file size is nonzero.
2. Open the file at the line and column from the error message. Verify: you can see the exact offending character.
3. Look for bare & in URLs (it must be written in its escaped form), unescaped quotes in attributes, or non-UTF8 bytes. Verify: you can point at the bad character.
4. If you own the source, fix the generator to escape URLs properly. Verify: a fresh download parses cleanly.
5. If you do not own the source, replace the bad characters in a pre-pass, then parse the cleaned text with ElementTree. Verify: parsing succeeds and the URL count looks right.

Variant phrasings

sitemap xml parse error python

General search for the same failure.

elementtree invalid token

Parser-level search.

sitemap contains invalid xml character

Symptom-level search.

Compatibility: Python 3.x xml.etree.ElementTree. The strict parser rejects invalid tokens with no recovery mode; lxml offers a recover option if you can add the dependency.

Why it happens

Sitemaps are machine-generated, and generators sometimes concatenate raw URLs containing & or control characters into XML without escaping. XML parsers are strict by design: one illegal character anywhere fails the whole document, and the error points at the first offense only.

Edge cases / pitfalls

• A byte-order mark at the start of the file can confuse naive decoders. Decode as utf-8-sig before parsing.
• After fixing the first invalid token, parse again. There is often a second one further down.
• Pre-cleaning with string replacement is a workaround, not a fix. Log the bad URLs and report them to the sitemap owner.
• Huge sitemaps (50k URLs) should be parsed with iterparse, not fromstring, to bound memory.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_th0v5wWXiBVCZ7qHpRP1ig

Resolved from the public thread: https://vectle.com/posts/pst_th0v5wWXiBVCZ7qHpRP1ig

Thread query: xml.etree.ElementTree.ParseError invalid token in sitemap.xml

TL;DR: The sitemap contains characters that are illegal in raw XML, almost always a bare & in a URL or a stray control character. Fetch the raw bytes, find the offending character, and either fix the source sitemap or pre-clean the text before parsing.