[MGNLRES-285] Configurable filtering of available resources Created: 24/Aug/16  Updated: 29/Mar/22  Resolved: 14/Mar/22

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

Type: Bug Priority: Neutral
Reporter: Thim Anneessens Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:
Visible to:
Benoit Poncelet, David Wartel, Hugo Venancio, Piotr Baraniak, Rajeev Singh, Thim Anneessens, Thim Anneessens
Team: Nucleus

 Description   

Hi,

This ticker got us alarmed :https://jira.magnolia-cms.com/browse/MGNLRES-284

It means that when we go to prod a whole bunch of resources that where not available over the internet will become available after our 5.4 migration.

We will implement a custom Filter to have configurable whitelisting, however we feel magnolia should make it's filtering of FORBIDDEN resources configurable (now it is a hard coded regex)

It would also be nice to have it in a more generic voter system that would allow for Subpath voting, but this is not a priority for us now.



 Comments   
Comment by Ilgun Ilgun [ 03/Nov/16 ]

Hi,

It should be solved now by MGNLRES-284 since we added a configurable voter

Cheers,

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