You don't have permission to access /dispatcher/invalidate.cache | Community
Skip to main content
D
dragon2A
Level 5
June 30, 2016
Solved

You don't have permission to access /dispatcher/invalidate.cache

  • June 30, 2016
  • 2 replies
  • 10920 views

Hi Hello Everyone,

 

 I am facing some issue with dispatcher invalidate cache. 

30.06.2016 16:11:41 - >> GET /dispatcher/invalidate.cache HTTP/1.0
30.06.2016 16:11:41 - >> CQ-Action: Test
30.06.2016 16:11:41 - >> CQ-Handle: /content
30.06.2016 16:11:41 - >> CQ-Path: /content
30.06.2016 16:11:41 - >> Referer: about:blank
30.06.2016 16:11:41 - >> Content-Length: 0
30.06.2016 16:11:41 - >> Content-Type: application/octet-stream
30.06.2016 16:11:41 - --
30.06.2016 16:11:41 - << HTTP/1.1 403 Forbidden
30.06.2016 16:11:41 - << Date: Thu, 30 Jun 2016 16:11:45 GMT
30.06.2016 16:11:41 - << Server: Apache/2.4.18 (Unix) Communique/4.1.11
30.06.2016 16:11:41 - << Content-Length: 236
30.06.2016 16:11:41 - << Content-Type: text/html; charset=iso-8859-1
30.06.2016 16:11:41 - << 
30.06.2016 16:11:41 - << <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
30.06.2016 16:11:41 - << <html><head>
30.06.2016 16:11:41 - << <title>403 Forbidden</title>
30.06.2016 16:11:41 - << </head><body>
30.06.2016 16:11:41 - << <h1>Forbidden</h1>
30.06.2016 16:11:41 - << <p>You don't have permission to access /dispatcher/invalidate.cache
30.06.2016 16:11:41 - << on this server.<br />
30.06.2016 16:11:41 - << </p>
30.06.2016 16:11:41 - << </body></html>
30.06.2016 16:11:41 - Message sent.

This is agent is in authoring server.

I am getting this error in production . The situation here is publisher and dispatcher in different servers. I am able to cache but while hitting the dispatcher from the authoring instance I am getting this. In other environments its working perfectly fine. Only this environment I am facing this issue. Any idea how to solve this?

Its very urgent. Basically I don't have time. I have tried all options. 

 

Thanks In Advance.

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 dragon2A

We figured it out. In dispatcher client section is restring to the localhost. we need to add allow for that section.

 

Here is the change

 

 /allowedClients
        {
        # Uncomment the following to restrict activation requests to originate
        # from "localhost" only.
        #
        /0000
          {
          /glob "*"
          /type "allow"
          }

2 replies

D
dragon2AAuthorAccepted solution
Level 5
July 1, 2016

We figured it out. In dispatcher client section is restring to the localhost. we need to add allow for that section.

 

Here is the change

 

 /allowedClients
        {
        # Uncomment the following to restrict activation requests to originate
        # from "localhost" only.
        #
        /0000
          {
          /glob "*"
          /type "allow"
          }

    Tuhin_Ghosh
    Tuhin_Ghosh
    Level 8
    July 4, 2016

    Hi,

     

    Please mark this  as solved if its already solved.

    Terms & ConditionsAccessibility statement

    Loading footer...