[MAGNOLIA-1695] Calendar resources throw 404 Created: 22/Aug/07 Updated: 10/Sep/08 Resolved: 10/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | zam6ak | Assignee: | Magnolia International |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
3.1-SNAPSHOT |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
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 |
| Comments |
| Comment by Magnolia International [ 10/Sep/08 ] |
|
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:
<error-page>
<error-code>404</error-code>
<location>/errors/404.html</location>
</error-page>
.. and upon request of an unexisting resource, Magnolia would serve your /error/404 page. 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 |