Implement new origin-based ResourcesServlet (MGNLRES-144)

[MGNLRES-161] Integration test for ResourcesServlet Created: 29/May/15  Updated: 03/Jul/15  Resolved: 30/Jun/15

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.4

Type: Sub-task Priority: Neutral
Reporter: Magnolia International Assignee: Michael Mühlebach
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:
Team: Nucleus

 Description   

The test on the feature/MGNLRES-144-resource-servlet-integration-test branch doesn't test much - 6 resources, all on the same origin (the least "interesting" of all, LegacyClasspathOrigin, ie /mgnl-resources/), and all accepted. If anything, we'd need tests that validate the scenarios we're trying to cover with this new features - hotfixes/overrides, serving resources from the different origins, making sure the error codes are ok, cache headers (with the help of the cache filter) are set correctly on author/public with/without devmode etc etc.



 Comments   
Comment by Michael Mühlebach [ 18/Jun/15 ]

gjoseph On branch feature/MGNLRES-161-resource-integration-test in project ce-bundle.

Comment by Magnolia International [ 30/Jun/15 ]

For those observing the "history" of this ticket: it was not actually reviewed. I gave it a quick over-the-shoulder look so Michi could proceed with merging it on master, so we'd actually start executing this test.
I'll now go through with the review and suggest future improvements (I think we discussed a few already, but no trace of it, so I'll start over)

Generated at Mon Feb 12 06:47:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.