title: AEM IIS dispatcher flush 403
body: <p>I'm getting a 403 error when I try to set up dispatcher flush through author in IIS. I'm fairly certain I need to set up authentication for the AEM author instance in IIS but I'm not sure which steps to take to do that. I've looked at Authentication for the site and anonymous authentication is set to Application Pool Identity. The dispatcher flush user is set to replication-receiver so I'm a little confused as to why IIS is reporting the user is anonymous.
  How do I allow my author instance to get access to /dispatcher/invalidate.cache?
  I've also looked at my dispatcher cache and I'm not seeing the dispatcher folder or invalidate.cache. Is this something that will appear once the permissions are resolved?</p>
  
  <p>Stackoverflow won't let me post links so I've put a Q in front of all the links. That doesn't appear in the log.</p>
  
  <p>IIS log:
  2016-10-14 18:09:37 999.999.999.999 GET /dispatcher/invalidate.cache - 80 - 999.999.999.999 Jakarta+Commons-HttpClient/3.1 about:blank 403 0 0 1</p>
  
  <p>AEM test log:
  Replication test to Qhttp://www.myproject.ca:80/dispatcher/invalidate.cache</p>
  
  <p>14.10.2016 18:11:09 - Create new HttpClient for Production Dispatcher Flush</p>
  
  <p>14.10.2016 18:11:09 - * Auth User: replication-receiver</p>
  
  <p>14.10.2016 18:11:09 - * HTTP Version: 1.1</p>
  
  <p>14.10.2016 18:11:09 - adding header: CQ-Action:Test</p>
  
  <p>14.10.2016 18:11:09 - adding header: CQ-Handle:/content</p>
  
  <p>14.10.2016 18:11:09 - adding header: CQ-Path:/content</p>
  
  <p>14.10.2016 18:11:09 - deserialize content for delivery</p>
  
  <p>14.10.2016 18:11:09 - No message body: Content ReplicationContent.VOID is empty</p>
  
  <p>14.10.2016 18:11:09 - Sending GET request to Qhttp://www.myproject.ca:80/dispatcher/invalidate.cache</p>
  
  <p>14.10.2016 18:11:09 - sent. Response: 403 Forbidden</p>
  
  <p>14.10.2016 18:11:09 - Replication (TEST) of /content not successful. Conversation follows</p>
  
  <p>14.10.2016 18:11:09 - ------------------------------------------------</p>
  
  <p>14.10.2016 18:11:09 - Sending message to www.myproject.ca:80</p>
  
  <p>14.10.2016 18:11:09 - >> GET /dispatcher/invalidate.cache HTTP/1.0</p>
  
  <p>14.10.2016 18:11:09 - >> CQ-Action: Test</p>
  
  <p>14.10.2016 18:11:09 - >> CQ-Handle: /content</p>
  
  <p>14.10.2016 18:11:09 - >> CQ-Path: /content</p>
  
  <p>14.10.2016 18:11:09 - >> Referer: about:blank</p>
  
  <p>14.10.2016 18:11:09 - >> Content-Length: 0</p>
  
  <p>14.10.2016 18:11:09 - >> Content-Type: application/octet-stream</p>
  
  <p>14.10.2016 18:11:09 - --</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; HTTP/1.1 403 Forbidden</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Cache-Control: private</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Content-Type: text/html; charset=utf-8</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Server: Microsoft-IIS/8.5</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Date: Fri, 14 Oct 2016 18:11:09 GMT</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; HTTP Error 403.0 - Forbidden</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; You do not have permission to view this directory or page.</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Most likely causes:</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; This is a generic 403 error and means the authenticated user is not authorized to view the page.</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Things you can try:</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, Qhttp://go.microsoft.com/fwlink/?LinkID=66439</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Detailed Error Information:</p>
  
  <p>14.10.2016 18:11:09 - Module</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Notification &nbsp;&nbsp;&nbsp;ExecuteRequestHandler</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Handler &nbsp;&nbsp;&nbsp;AEM</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Error Code &nbsp;&nbsp;&nbsp;0x00000000</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Requested URL &nbsp;&nbsp;&nbsp; Qhttp://www.myproject.ca:80/dispatcher/invalidate.cache</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Physical Path &nbsp;&nbsp;&nbsp;C:\inetpub\wwwroot\dispatcher\invalidate.cache</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Logon Method &nbsp;&nbsp;&nbsp;Anonymous</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Logon User &nbsp;&nbsp;&nbsp;Anonymous</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; More Information:</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; This generic 403 error means that the authenticated user is not authorized to use the requested resource. A substatus code in the IIS log files should indicate the reason for the 403 error. If a substatus code does not exist, use the steps above to gather more information about the source of the error.</p>
  
  <p>14.10.2016 18:11:09 - &lt;&lt; Qhttp://go.microsoft.com/fwlink/?LinkID=62293&amp;IIS70Error=403,0,0x00000000,9600 View more information</p>
  
  <p>14.10.2016 18:11:09 - Message sent.</p>
  
  <p>14.10.2016 18:11:09 - ------------------------------------------------</p>
  
  <p>14.10.2016 18:11:09 - Replication (TEST) of /content not successful.
  Replication test failed
  Forbidden</p>