Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Dispatcher | Filter changes are not working on PROD but working on Lower environments

Avatar

Community Advisor

Hi Team, 

Recently we have made a few changes in the filter rules to deny the cross-site content in the current domain. The other filter rules are working fine in PROD but other site content is still accessible on the current domain.

Ex: 

domain 1:  www.abc.com/

content path of domain1: /content/abc/us/en/test.html

 

domain 1:  www.xyz.com/

content path of domain1: /content/xyz/us/en/test.html

 

if we try to access www.abc.com/content/xyz/us/en/test.html it should not render as an original page it should throw 404 and vice versa.

 

We made changes in the dispatcher at the domain level denying everything and allowing only the content specific to that site

These changes are working fine in all lower environments but not on PROD. 

 

Please provide your thoughts on this!!

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @sravs ,

There might be following reason-

1. Any environment-specific configurations that might differ. This includes URLs, IP addresses, or environment-specific variables.

2. If any load balancer or reverse proxy in production, ensure that its configuration aligns with dispatcher rules.

3. Hope dispatcher deployment successfully completed, better re do dispatcher deployment

4. Cached pages might be getting served so try by adding query param in url once once.

Thanks

View solution in original post

3 Replies

Avatar

Community Advisor

Hi @sravs ,

 

Can you please share the dispatch log or review the dispatcher logs in production for any errors or warnings related to the filter rules.

Avatar

Correct answer by
Community Advisor

Hi @sravs ,

There might be following reason-

1. Any environment-specific configurations that might differ. This includes URLs, IP addresses, or environment-specific variables.

2. If any load balancer or reverse proxy in production, ensure that its configuration aligns with dispatcher rules.

3. Hope dispatcher deployment successfully completed, better re do dispatcher deployment

4. Cached pages might be getting served so try by adding query param in url once once.

Thanks

Avatar

Community Advisor

Can you cross check your ServerName and ServerAlias properties in your vhost files once ? And share the dispatcher logs if possible.