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 cache invalidation not working locally

Avatar

Level 7

Hi,

I have the dispatcher installed locally and I can access published sites through it, but cache invalidation is not working. In short, its endpoint return 404 Not Found.

In the dispatcher.any, the filter section is configured to allow /0030 { /type "allow" /url "/dispatcher/invalidate.cache" }.

After enabling the flush agent, clicking test logs this:

Replication test to http://localhost:8080/dispatcher/invalidate.cache

18.02.2015 12:00:11 - Create new HttpClient for Dispatcher Flush
18.02.2015 12:00:11 - * HTTP Version: 1.1
18.02.2015 12:00:11 - adding header: CQ-Action:Test
18.02.2015 12:00:11 - adding header: CQ-Handle:/content
18.02.2015 12:00:11 - adding header: CQ-Path:/content
18.02.2015 12:00:11 - deserialize content for delivery
18.02.2015 12:00:11 - No message body: Content ReplicationContent.VOID is empty
18.02.2015 12:00:11 - Sending GET request to http://localhost:8080/dispatcher/invalidate.cache
18.02.2015 12:00:11 - sent. Response: 404 Not Found
18.02.2015 12:00:11 - Replication (TEST) of /content not successful. Conversation follows
18.02.2015 12:00:11 - ------------------------------------------------
18.02.2015 12:00:11 - Sending message to localhost:8080
18.02.2015 12:00:11 - >> GET /dispatcher/invalidate.cache HTTP/1.0
18.02.2015 12:00:11 - >> CQ-Action: Test
18.02.2015 12:00:11 - >> CQ-Handle: /content
18.02.2015 12:00:11 - >> CQ-Path: /content
18.02.2015 12:00:11 - >> Referer: about:blank
18.02.2015 12:00:11 - >> Content-Length: 0
18.02.2015 12:00:11 - >> Content-Type: application/octet-stream
18.02.2015 12:00:11 - --
18.02.2015 12:00:11 - << HTTP/1.1 404 Not Found
18.02.2015 12:00:11 - << Date: Wed, 18 Feb 2015 01:00:11 GMT
18.02.2015 12:00:11 - << Server: Apache/2.4.7 (Unix) Communique/4.1.5
18.02.2015 12:00:11 - << Content-Length: 225
18.02.2015 12:00:11 - << Content-Type: text/html; charset=iso-8859-1
18.02.2015 12:00:11 - << 
18.02.2015 12:00:11 - << <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
18.02.2015 12:00:11 - << <html><head>
18.02.2015 12:00:11 - << <title>404 Not Found</title>
18.02.2015 12:00:11 - << </head><body>
18.02.2015 12:00:11 - << <h1>Not Found</h1>
18.02.2015 12:00:11 - << <p>The requested URL /dispatcher/invalidate.cache was not found on this server.</p>
18.02.2015 12:00:11 - << </body></html>
18.02.2015 12:00:11 - Message sent.
18.02.2015 12:00:11 - ------------------------------------------------
18.02.2015 12:00:11 - Replication (TEST) of /content not successful.

Any ideas what is probably not configured properly?

1 Accepted Solution

Avatar

Correct answer by
Level 10

The SetHandler directive that configures webserver to forward dispatcher requests to dispatcher handler missing causes such issue. Verify your httpd.conf if it is apache and looking at filter is a wrong direction.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

The SetHandler directive that configures webserver to forward dispatcher requests to dispatcher handler missing causes such issue. Verify your httpd.conf if it is apache and looking at filter is a wrong direction.