[MAGNOLIA-7839] contentType Filter Not Bypass-able Created: 01/Jul/20  Updated: 11/Mar/21

Status: Open
Project: Magnolia
Component/s: configuration
Affects Version/s: 6.2.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Chris Jennings Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-6217 Review names and "duties" of Filters Open
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

 Description   

The filter contentType (an instance of ContentTypeFilter) cannot be bypassed.

Filter voting relies on the currentURI which is not set until this filter is executed. Therefore, no voter can trigger a bypass.

A bypass is configured: /server/filters/contentType/bypasses/vaadinPush but actually does nothing. I would argue the bypass should at least be removed as it is misleading.

Discussed in #Support channel, 30 June 2020. See:
https://magnolia-cms.slack.com/archives/CC1GVEGFP/p1593526291291900


Generated at Mon Feb 12 04:27:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.