Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

preetivardhanb9
preetivardhanb9
Offline

Badges

Badges
5

Accepted Solutions

Accepted Solutions
0

Likes

Likes
1

Posts

Posts
5

Discussions

Discussions
3

Questions

Questions
2

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by preetivardhanb9
Customize the badges you want to showcase on your profile
Re: Dispatcher rewrite rule based on the source IP/Domain
Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,406 likes

Total Posts

3,352 posts

Correct reply

1,138 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
- Adobe Experience Manager
Are you sure that the correct virtualhost is used? Have you put the statement "RewriteEngine on" in front of these rules?

Views

230

Likes

0

Replies

0
Re: AEM Dispatcher cache invalidate
Avatar
Give Back
Level 2
preetivardhanb9
Level 2

Like

1 like

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back
Ignite 3
Ignite 1
Validate 1
Boost 1
View profile
preetivardhanb9
- Adobe Experience Manager
Thank you so much. I'll check it out.

Views

719

Likes

0

Replies

0
Re: AEM 6.4
Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,406 likes

Total Posts

3,352 posts

Correct reply

1,138 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
- Adobe Experience Manager
do you get that message from the httpd or from AEM?And is the $Server_hostname really identical to the one you used in the request? You can increase the loglevel of the dispatcher to DEBUG to see if the dispatcher is consulted for this request or if the problem is the httpd itself. And in that case the dispatcher also logs enough information to see what AEM is doing; just addDispatcherLogLevel 3into the section and restart the httpd.

Views

599

Likes

0

Replies

0
Likes from