[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649337#action_12649337
]
Vidar S. Ramdal commented on SLING-249:
---------------------------------------
Great that you're taking this task :)
What about resources that should be shared among domains?
Let's say "domain root nodes" are stored under /content/domain1.com,
/content/domain2.com etc.
There might be some scripts, CSS, graphics etc that we want to be available for
all hosts, let's say they're stored under /shared. When rendering HTML for the
root node of http://domain1.com, we want to link to /shared/style.css. This
means the web browser sends a request to the server, including the Host header
- which will cause Sling to look for /content/domain1.com/shared/style.css -
which does not exist.
> Allow mapping nodes to internet domains
> ---------------------------------------
>
> Key: SLING-249
> URL: https://issues.apache.org/jira/browse/SLING-249
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: JCR Resource 2.0.2
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> Sling should support hosting multiple domains, with different JCR roots.
> E.g.:
> http://www.domain1.com could map to /content/domain1.com
> http://www.domain2.com could map to /content/domain2.com
> While developing a website, the fully qualified domain might not be
> available. Ideally, the mapping could be configured in a flexible way. One
> option would be to maintain a set of regular expressions to match against
> URLs. Each regexp would then match to a path in the JCR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
