Dispatcher cache invalidation not working locally | Community
Skip to main content
LinearGradient
Level 6
October 16, 2015
Solved

Dispatcher cache invalidation not working locally

  • October 16, 2015
  • 1 reply
  • 2195 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

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.

1 reply

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

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.