How to achieve 404 scenario in TeamSite pages

Kapil_sape

Hi,

404 scenarios are very common in any web-sites.
We are building web-site using TS 7.2.1, Livesite 7.2.1 and application is running on Dotnet controls. We are creating pages using SitePublisher components.

In such case how to handle 404 errors. One recommendation could be:

On a very high level create a "page not found.page" file in TeamSite and redirect to this page via web.config file of Dotnet control as and when 404 request comes.

I am not aware of Dotnet so is this a right approach or there can be a better way to achieve this.

Help or suggestions are much appreciated.

Thanks,
Kapil

Bowker

I have been playing around with "file not found" type of errors this week and have found that there are at least 2 different errors you can get, 404 and 490 [sic].

404 - (empirical evidence only) the rewrite rules on the application server that runs LiveSite only forwards URIs that end in .page or that appear to be a directory reference (No periods in last portion). Therefore redirecting the 404 condition (missing image or document) is, I believe, being handled by the configuration of the app server. LiveSite ships with TomCat.

-- Side note: I just created an alias with a period in it (****/fn.ln). SitePublisher accepted it, but it didn't work after publishing. So my theory above still holds.

490 - (this one I've done extensive looking into) If there is no alias defined for the given URI, that doesn't contain a period, then LiveSite will through a 490 error and redirect to InvalidSite.jsp. From there you can do what you want (see my other recent posts about this page)

Not sure if that helps, but it's information that other's may find useful.