AEM 6.2 Dispatcher Configuration to access DAM on Publisher

[jasminec3059355]

HI,

I am setting up dispatcher for publisher and need to access DAM folder from the publisher.  However, I got filter rejected error:

[Thu Mar 22 13:34:29 2018] [D] [pid 15924] Filter rejects: GET /assets.html/content/dam/ HTTP/1.1

Here is the filter section in dispatcher.any file:

/filter

      {

      # Deny everything first and then allow specific entries

      /0001 { /type "deny" /glob "*" }

      # Open consoles

#     /0011 { /type "allow" /url "/admin/*"  }  # allow servlet engine admin

#     /0012 { /type "allow" /url "/crx/*"    }  # allow content repository

#     /0013 { /type "allow" /url "/system/*" }  # allow OSGi console

      # Allow non-public content directories

#     /0021 { /type "allow" /url "/apps/*"   }  # allow apps access

#     /0022 { /type "allow" /url "/bin/*"    }

      /0023 { /type "allow" /glob "*/content*" }  # disable this rule to allow mapped content only

     /0024 { /type "allow" /url "/libs/*"   }

#     /0025 { /type "deny"  /url "/libs/shindig/proxy*" } # if you enable /libs close access to proxy

#     /0026 { /type "allow" /url "/home/*"   }

#     /0027 { /type "allow" /url "/tmp/*"    }

#     /0028 { /type "allow" /url "/var/*"    }

      # Enable extensions in non-public content directories, using a regular expression

      /0041

        {

        /type "allow"

        /extension '(clientlibs|css|gif|ico|js|png|swf|jpe?g|woff2?)'

        }

      # Enable features

      /0062 { /type "allow" /url "/libs/cq/personalization/*"  }  # enable personalization

      # Deny content grabbing, on all accessible pages, using regular expressions

      /0081

        {

        /type "deny"

        /selectors '((sys|doc)view|query|[0-9-]+)'

        /extension '(json|xml)'

        }

      # Deny content grabbing for /content

      /0082

        {

        /type "deny"

        /path "/content"

        /selectors '(feed|rss|pages|languages|blueprint|infinity|tidy)'

        /extension '(json|xml|html)'

        }

      # Uncomment the following to allow one-level json requests

      #/0087 { /type "allow" /method "GET" /extension "json" /selectors "1" }

      }

Can someone help me on the configuration?

Thanks in advance.

[Kunwar · Accepted solution]

I think this would be expected coz in Publishers we have deny all and allow some strategy. The first rules in your publisher config denies everything and if want to allow /assets.html/, you need to allow this.

A quick question, any specific reason you need to access assets from the publish instance ? Wouldn't you rely on publishing of assets from author to publish. Just curious to know the use-case