[CONFSERVER-14319] Excpetion "not legal for a JDOM character content: 0x1d is not a legal XML character." in RSS feed

Type: Bug
Resolution: Fixed
Priority: Medium
Fix Version/s: 3.1
Affects Version/s: 2.10
Component/s: None
Labels:
- affects-server
- qa-triage
Environment:

seen in EAC

Bug Fix Policy:
View Atlassian Server bug fix policy

My RSS returns an error page with:

org.jdom.IllegalDataException: The data "ABOUT 30 pages of text" is not legal for a JDOM character content: 0x1d is not a legal XML character.

Feed URL is
http://extranet.atlassian.com/createrssfeed.action?types=page&types=blogpost&types=mail&types=comment&sort=modified&showContent=true&showDiff=true&spaces=conf_favorites&spaces=conf_personal&labelString=&rssType=atom&maxResults=50&timeSpan=10&publicFeed=false&title=EAC+feed&os_authType=basic

is duplicated by

CONFSERVER-15569 Certain unicode characters in a page will break RSS feeds

Closed

relates to

CONFSERVER-13285 Axis webservice may be asked to deliver invalid XML characters

Closed

David Taylor (Inactive) added a comment - 09/Oct/2009 6:35 AM

Andrew gave changes from review the nod.

David Taylor (Inactive) added a comment - 09/Oct/2009 6:35 AM Andrew gave changes from review the nod.

Anatoli added a comment - 09/Jul/2009 5:19 AM

Changed the 'fix for' version as this is not going to be implemented for 3.0.1.

Anatoli added a comment - 09/Jul/2009 5:19 AM Changed the 'fix for' version as this is not going to be implemented for 3.0.1.

Anatoli added a comment - 04/Jun/2009 1:30 AM

It is not a straight forward fix as we already encode some characters when we render template (the result of the rendering is used for generating RSS). So if we try to xml encode the output we end up with double encoding.

Anatoli added a comment - 04/Jun/2009 1:30 AM It is not a straight forward fix as we already encode some characters when we render template (the result of the rendering is used for generating RSS). So if we try to xml encode the output we end up with double encoding.

Per Fragemann [Atlassian] added a comment - 24/Feb/2009 7:24 AM

maybe something for the bugfixing team. very unlikely to be a 3.0 specific bug though

Per Fragemann [Atlassian] added a comment - 24/Feb/2009 7:24 AM maybe something for the bugfixing team. very unlikely to be a 3.0 specific bug though

Assignee:: David Taylor (Inactive)

Reporter:: Matt Quail (Inactive)

Affected customers:: 1 This affects my team

Watchers:: 2 Start watching this issue

Created:: 29/Jan/2009 12:21 AM

Updated:: 11/Oct/2018 8:46 AM

Resolved:: 09/Oct/2009 6:37 AM

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: David Taylor (Inactive) added a comment - 09/Oct/2009 6:35 AM

Expand comment: David Taylor (Inactive) added a comment - 09/Oct/2009 6:35 AM

Collapse comment: Anatoli added a comment - 09/Jul/2009 5:19 AM

Expand comment: Anatoli added a comment - 09/Jul/2009 5:19 AM

Collapse comment: Anatoli added a comment - 04/Jun/2009 1:30 AM

Expand comment: Anatoli added a comment - 04/Jun/2009 1:30 AM

Collapse comment: Per Fragemann [Atlassian] added a comment - 24/Feb/2009 7:24 AM

Expand comment: Per Fragemann [Atlassian] added a comment - 24/Feb/2009 7:24 AM

People

Dates