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

Gregory Joseph commented on MAGNOLIA-1565:
------------------------------------------

Since 3.5, the ERROR dispatcher is assigned to the main Magnolia filter by 
default. If that's the case in your setup too, the 404 page in your web.xml 
needs to be reachable through Magnolia. Typically, you could have this in your 
web.xml: 
{noformat} 
  <error-page>
    <error-code>404</error-code>
    <location>/errors/404.html</location>
  </error-page>
{noformat} .. and upon request of an unexisting resource, Magnolia would serve 
your /error/404 page.

Now, as far as I can tell, there is no other way than mapping all error codes 
in web.xml - we could do so by default, and a have location like 
{{/.magnolia/error}} which would take care, based on some configuration, render 
the configured page for the different codes, but
* is it really worth it ? i.e how much configuration will one be ready to do 
when it can be done directly in web.xml ? - (if there was a way to map "all" 
error codes to locations, I'd love it but as far as i can tell you have to map 
each and every error code separately)
* as far as I can tell, when serving an error page, you can't really know what 
the error code and message were (unless i've missed the obvious)


Any suggestion ?

> Allow error pages (401,404,500 etc,etc) to be configured as Magnolia pages
> --------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-1565
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1565
>             Project: Magnolia
>          Issue Type: New Feature
>         Environment: 3.1-SNAPSHOT
> JBoss 4.0.5
>            Reporter: Amir Mistric
>            Assignee: Boris Kraft
>            Priority: Minor
>
> While discussing error page locations with Sameer (via dev list and support), 
>  it was suggested that this feature may make it into next version.
> The goal would be to mimic web.xml error page logic where one can define an 
> error code or exception (or both) and specify Magnolia page that should be 
> displayed when such error/exception occurs.

-- 
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