When I modify the site evaluation rules I still get valid page links when added in the ckEditor
(MULTISITE-48)
|
|
| Status: | Closed |
| Project: | Magnolia Multisite Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.4, 1.2.3 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Philip Mundt | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | documentation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Release notes required: |
Yes
|
||||||||||||
| Sprint: | Basel 29 | ||||||||||||
| Description |
|
uri-starts-with-sitename rules is mainly there to enable serving all sites when working in an admin instance (where access might indeed happen through one domain) – identified by the site prefix, e.g. http://www.demo-features.com/demo-project/about/subsection-articles/article.html where demo-project identifies the site-name but www.demo-features.com is mapped to the actual demo-features site. To evaluate:
See related support issue for a thorough description. Suggested solutionWe provide an AdminOnlyMatcher that only matches on the author-instance (checking the ServerConfiguration). With the matcher one can limit the evaluation of the problematic rule uri-starts-with-sitename to be active on admin only, preventing cross-site-access via <sitename> prefix on the public instance. NotesWe do not install this by default as it might prevent the bundle from working on localhost – as our demo sites and domains might not be fully configured. To use this matcher it simply has to be set on the rule uri-starts-with-sitename as an additional matcher. See |
| Comments |
| Comment by Philip Mundt [ 01/Feb/16 ] |
|
To QA:
|