[
http://jira.magnolia.info/browse/MAGNOLIA-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Joseph closed MAGNOLIA-1695.
------------------------------------
Resolution: Obsolete
Assignee: Gregory Joseph (was: Boris Kraft)
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.
If you don't have the ERROR dispatcher for the main Magnolia filter, the
location of {{<error-page>}} should point to a resource available in your
webapp (a .jsp, for example)
Now, the URI you give as a sample should indeed return a 404 since there is no
such resource (calendar-en.js or calendar-de.js would work, but not
calendar-.js)
Please reopen if I'm missing something :)
> Calendar resources throw 404
> ----------------------------
>
> Key: MAGNOLIA-1695
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1695
> Project: Magnolia
> Issue Type: Bug
> Environment: 3.1-SNAPSHOT
> Reporter: Amir Mistric
> Assignee: Gregory Joseph
>
> prerequisite: Define a 404 page in web.xml
> If you click on any of the menus you will get:
> Status Code: 404 - URI: /magnoliaAuthor/.resources/calendar/lang/calendar-.js
--
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/
----------------------------------------------------------------
