[MAGNOLIA-2135] Public instance: repository content filtered based on virtualhost Created: 13/May/08  Updated: 23/Jan/13  Resolved: 21/Mar/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.4
Fix Version/s: 4.3.1

Type: Improvement Priority: Major
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2132 One Magnolia to rule them all Closed
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)
Date of First Response:

 Description   

Related to MAGNOLIA-2134:
we should also provide a way to "filter" content in the website repository, making trees for different websites hidden for specific virtualhost.
For example if we use a single public instance in order to serve site-one and site-two we would like to accept requests for:
http://www.site-one.xxx/site-one/home.html
but not for
http://www.site-one.xxx/site-two/home.html



 Comments   
Comment by Philipp Bracher [ 14/May/08 ]

We could also think about rewriting the links by using info.magnolia.cms.link.LinkResolver. To do so we would have to improve that a bit (something I wanted to do since a long time).

The rendering would create a link like /home.html while the rendered content would resist in /site/home. Using this one could avoid the /site/ in the paths.

Comment by Fabrizio Giustina [ 19/Aug/09 ]

Added a new info.magnolia.cms.filters.HostSecurityFilter that can be used for this scenario. Configuration details added to javadocs.

Comment by Fabrizio Giustina [ 21/Mar/10 ]

reopening, the class was incorrectly added to the test folder

Comment by Fabrizio Giustina [ 21/Mar/10 ]

marking as resolved in 4.3.1

Generated at Mon Feb 12 03:33:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.