[Seaside] Handling not found

Philippe Marschall philippe.marschall at gmail.com
Sun Oct 20 13:27:20 UTC 2013

On Fri, Oct 18, 2013 at 8:32 AM, Torsten Bergmann <astares at gmx.de> wrote:
> Hi,
> running a simple seaside demo app using Seaside with Zinc (ZnZincServerAdaptor) and Pharo.
> Its available from
>   http://localhost:8080/myapp
> and (since I changed the default) also on
>   http://localhost:8080
> When entering
>   http://localhost:8080/somethingtotallyunknown
> I get a 'not found' which seems to be handled by default in WAResponseGenerator>>notFound.
> I would like to have a nice page when nothing is found. Since it should run standalone
> I dont want to catch 404 at the front (apache, nginx) but directly in seaside to redirect
> to a nice "You are lost" page.
> How can I register an own #responseGenerator that can handle 404?

It should be a configured on the default dispatcher or the default
application (depending on which one sends #notFound) like any other
configuration option.


More information about the seaside mailing list