Error page

I'm trying to understand how to configure our RunTime environment's error pages. From what I can tell there are at least three different responses you can get for a request for a page that doesn't exist.

1) if you go to /site/abc.pdf and it doesn't exist you get a 404 back from TomCat.

2) if you go to /site/abc.page and it doesn't exist you get the page that's been configured in the site details for "error".

3) if you go to /site/abc (no extension) you get a page that reads " (-) The site you requested (-Invalid Site-) is invalid. Please select a site " and a drop down for each of the defined sites on the server.

I would like to change the functionality of both cases 1 and 3. Any suggestions on where these can be changed?

(more information found)
For case 3 in /opt/interwoven/LiveSiteDisplayServices/runtime/tomcat/logs/livesite.runtime.log I found these two lines:

2011-08-29 09:28:51,732 ERROR [com.interwoven.livesite.runtime.rendering.RuntimeRenderingManager] render: handleException(RenderingException)
2011-08-29 09:28:51,732 ERROR [com.interwoven.livesite.runtime.rendering.RuntimeRenderingManager] doFilter: site not valid:

Find more posts tagged with

Comments

Bowker

Well after digging through Interwoven's code (livesite-runtime.jar) I found that if you have an invalid alias the method handleInvalidSite is called.

RenderingManager.handleInvalidSite() does a forward action to /iw/errors/InvalidSite.jsp.

Looking in the support site for "handleInvalidSite" [do you mean Handle InvalidSite?] it says:

Redirecting request for non .page files to the InvalidSite.jsp is the default behaviour. You could modify the /runtime/web/iw/errors/InvalidSite.jsp to either redirect to an existing custom 404 page or modify it directly.

https://customers.autonomy.com/support/secure/index.jsp#{"state":{"version":18,"sort":"Relevance+Date","Text":"handle invalidsite"},"datasource":"Solution","operation":"zoom","vstate":{"MatchReference":["/automater/automater_files/docs/Solutions/Interwoven/Teamsite - Client/3.1/767919.html"],"oldState":{"state":{"version":18,"sort":"Relevance+Date","Text":"handle invalidsite"},"datasource":"allTab","operation":"zoom"},"resultSetIndex":1,"resultSetSize":600,"links":"INVALIDSIT","text":["handle invalidsite"]}}

Looks like I can modify iw/errors/invalidSite.jsp

Charles8

Did you figure out how to handle the 404? We frequently move content and would like to direct the 404 request to the correct page. We keep track of pages that have been moved, but don't know how or where to execute the re-direct to the correct page. Any ideas?

Bowker

In the case of a generic 404 - we're not really concerned about those. We are handling "static content" elsewhere. But that can be corrected in the application server you are running LiveSite under. (TomCat for example)

IF you are moving aliases, or pages without any period in the path/filename then we are talking about the same thing. If you look at the response from those pages you will see the return code of 490.

The InvalidSite.jsp can be found on the TeamSite server here:
LiveSiteDisplayServices\runtime\web\iw\errors\InvalidSite.jsp

It needs to be copied to your LiveSite server here:
LiveSiteDisplayServices/runtime/web/iw/errors/InvalidSite.jsp

That JSP can do pretty much what ever you want. I have another post titled "Override RenderingManager" (or something close to that) that has some details on getting what page you came from.

Kapil_sape

Hi Bowker,

In default.site we can configure 'Error page' parameter. We have created a 'page not found.page' file and configured 'Error page: page not found.page'. Does this mean whenever a user hits sites/abc.page where abc.page does not exist it will get redirected to page not found.page.

Am I correct?

Thanks,
Kapil Jain