Red Hat Bugzilla – Bug 115015
New content item dispatcher doesn't support '.xml' suffix on contnet items
Last modified: 2007-04-18 13:02:34 EDT
Description of problem:
In 5.2 and prior, if you changed the filename extension used to refer
to a content item from '.jsp' to '.xml' then it would output the XML
representation of the content item instead of HTML. NB, this is not
the same as '?output=xml' because the former only output XML for the
item itself, where as the lkatter includes XML for the Bebop page and
all navigation elements.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Hmm. How should this interact with the ML changes. Among other things,
on 6.0 and later, the ".jsp" is now optional. So for an article foo
with English and Spanish versions, the following URLs are valid:
foo.jsp, foo -- return default language html
foo.en, foo.en.jsp, foo.jsp.en -- return english html
foo.es, foo.es.jsp, foo.jsp.es -- return spanish html
For ".xml", the following should be allowed:
foo.xml, foo.en.xml, and foo.es.xml
I'm not sure if we'll need to worry about other combinations.
Wow, I didn't know ML had soooo many suffix varieties. Just the simple
example you describe would be sufficient I reckon.
is this the same as bug 114104?
Yes, it does seem to be the same.
*** This bug has been marked as a duplicate of 114104 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.