[ 
http://jira.magnolia.info/browse/MAGNOLIA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165#action_16165
 ] 

Simon Goodchild commented on MAGNOLIA-2136:
-------------------------------------------

This would also be a useful function for the core system, even when not using 
vitualhosts, so we should make it generic enough to cope with a single site - 
maybe a "default" entry in addition to a mapping for each virtualhost? As the 
app server config requires the error codes to be mapped to a physical file 
within the webapp, maybe we could have a generic error.jsp file within the core 
distribution which calls a 'errorDispatcher' class in turn would:
- Identify the error code being flagged
- Identify the hostname the http request was targeted at
- Query a mapping table in the repository which points host+error to a specific 
page within the system
- If there is no mapping for the given combination it uses the default entry 
for the error code
- Then it redirects to the relevant URI

One issue would be whether we include these custom error pages within the 
actual site structure (would need to be hidden pages) or if we define some 
other node that they would all live under? Maybe we could have a convention of 
a site node called "error-pages" that is automatically ignored by the 
navigation tag to save having to set the hideInNav flag on every page?

Simon

> Public instance: different error pages for different virtualhost
> ----------------------------------------------------------------
>
>                 Key: MAGNOLIA-2136
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2136
>             Project: Magnolia
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.5.4
>            Reporter: Fabrizio Giustina
>            Assignee: Fabrizio Giustina
>
> Given that there is no real support for defining error pages in magnolia, we 
> are anyway using the default error page mapping in web.xml in order to 
> forward to magnolia-managed pages in case of 404 or errors.
> If we think about serving different websites on a single public magnolia 
> instance we should probably also find a way of defining different error pages 
> for different virtualhosts.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to