[opencms-dev] XMLContent: connection to JSP file result in 500 instead of 404

Roman Uhlig roman.uhlig at knve.de
Thu Sep 17 16:16:04 CEST 2009

XMLContent is often used for resources that change a lot, e.g. news. Thus
there is a lot of change regarding the available resources, which are
automatically numbered by OpenCms. So far so good. 

Now your site gets indexed by search engines, which will eventually try to
load XMLContent pages that are no longer existent because they expired or
got deleted. Especially with news type content this happens a lot. The only
way (or the only recommended way) to get these pages out of the search
engines index is to deliver a 404 response. Due to the nature of OpenCms'
coupling of XMLContent with a JSP file that is able to show the content, it
will throw an internal server error (500).

After a while search engines will produce a happy internal server error
throw fest.

Of course I could manually check for the existence of the requested xml
content in the corresponding JSP, but isn't there any OpenCms feature or
common procedure I might have missed that solves this issue?

Thanks in advance for any hints,
View this message in context: http://www.nabble.com/XMLContent%3A-connection-to-JSP-file-result-in-500-instead-of-404-tp25491911p25491911.html
Sent from the OpenCMS - Dev mailing list archive at Nabble.com.

More information about the opencms-dev mailing list