Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Which attribute must be present in all filter rules in AEM dispatcher configuration?

Avatar

Level 7

Hi Team,

 

Expecting the correct answer.

 

Which attribute must be present in all filter rules in AEM dispatcher configuration?

1. /glob

2. /type

3. /url

 

Thanks.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@JakeCham 

 

A filter is meant to convey allow or deny. So, /type is required.

 

/url and /glob are for pattern matching. Filtering with globs is deprecated in Dispatcher. As such, you should avoid using globs in the /filter sections since it may lead to security issues. So, instead of:

/glob "* *.css *"

use

/url "*.css"

 

So, you can use either of them or use /path instead. refer to https://blog.developer.adobe.com/writing-better-aem-dispatcher-filters-f23b391624a9 

 


Aanchal Sikka

View solution in original post

3 Replies

Avatar

Level 8

Hello,

 

You can refer the official dispatcher documentation for details - https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c..., but it looks to be the /type attribute that must be present in all filter rules.

 

Thanks

Narendra

Avatar

Community Advisor

Hi @JakeCham

The AEM dispatcher configuration attribute that must be present in all filter rules is "/type" only.

 

Thanks.



Avatar

Correct answer by
Community Advisor

@JakeCham 

 

A filter is meant to convey allow or deny. So, /type is required.

 

/url and /glob are for pattern matching. Filtering with globs is deprecated in Dispatcher. As such, you should avoid using globs in the /filter sections since it may lead to security issues. So, instead of:

/glob "* *.css *"

use

/url "*.css"

 

So, you can use either of them or use /path instead. refer to https://blog.developer.adobe.com/writing-better-aem-dispatcher-filters-f23b391624a9 

 


Aanchal Sikka