|
| 1 | +/weretail-publishfarm { |
| 2 | + ## client headers which should be passed through to the render instances |
| 3 | + ## (feature supported since dispatcher build 2.6.3.5222) |
| 4 | + /clientheaders { |
| 5 | + $include "/etc/httpd/conf.dispatcher.d/clientheaders/ams_publish_clientheaders.any" |
| 6 | + $include "/etc/httpd/conf.dispatcher.d/clientheaders/ams_common_clientheaders.any" |
| 7 | + } |
| 8 | + ## hostname globbing for farm selection (virtual domain addressing) |
| 9 | + /virtualhosts { |
| 10 | + we-retail |
| 11 | + we-retail.docker.local |
| 12 | + } |
| 13 | + ## the load will be balanced among these render instances |
| 14 | + /renders { |
| 15 | + $include "/etc/httpd/conf.dispatcher.d/renders/ams_publish_renders.any" |
| 16 | + } |
| 17 | + ## only handle the requests in the following acl. default is 'none' |
| 18 | + ## the glob pattern is matched against the first request line |
| 19 | + /filter { |
| 20 | + $include "/etc/httpd/conf.dispatcher.d/filters/weretail_filters.any" |
| 21 | + } |
| 22 | + ## if the package is installed on publishers to generate a list of all content with a vanityurl attached |
| 23 | + ## this section will auto-allow the items to bypass the normal dispatcher filters |
| 24 | + ## Reference: https://docs.adobe.com/docs/en/dispatcher/disp-config.html#Enabling%20Access%20to%20Vanity%20URLs%20-%20/vanity_urls |
| 25 | + #/vanity_urls { |
| 26 | + # /url "/libs/granite/dispatcher/content/vanityUrls.html" |
| 27 | + # /file "/tmp/vanity_urls" |
| 28 | + # /delay 300 |
| 29 | + #} |
| 30 | + ## allow propagation of replication posts (should seldomly be used) |
| 31 | + /propagateSyndPost "0" |
| 32 | + ## the cache is used to store requests from the renders for faster delivery |
| 33 | + ## for a second time. |
| 34 | + /cache { |
| 35 | + ## The cacheroot must be equal to the document root of the webserver |
| 36 | + /docroot "${PUBLISH_DOCROOT}" |
| 37 | + ## sets the level upto which files named ".stat" will be created in the |
| 38 | + ## document root of the webserver. when an activation request for some |
| 39 | + ## handle is received, only files within the same subtree are affected |
| 40 | + ## by the invalidation. |
| 41 | + /statfileslevel "${DEFAULT_STAT_LEVEL}" |
| 42 | + ## caches also authorized data |
| 43 | + /allowAuthorized "0" |
| 44 | + ## Flag indicating whether the dispatcher should serve stale content if |
| 45 | + ## no remote server is available. |
| 46 | + /serveStaleOnError "1" |
| 47 | + ## the rules define, which pages should be cached. please note that |
| 48 | + ## - only GET requests are cached |
| 49 | + ## - only requests with an extension are cached |
| 50 | + ## - only requests without query parameters ( ? ) are cached |
| 51 | + ## - only unauthorized pages are cached unless allowUnauthorized is set to 1 |
| 52 | + /rules { |
| 53 | + $include "/etc/httpd/conf.dispatcher.d/cache/ams_publish_cache.any" |
| 54 | + } |
| 55 | + # the invalidate section defines those pages which are 'invalidated' after |
| 56 | + # any activation. please note that, the activated page itself and all |
| 57 | + # related documents are flushed on an modification. for example: if the |
| 58 | + # page /foo/bar is activated, all /foo/bar.* files are removed from the |
| 59 | + # cache. |
| 60 | + /invalidate { |
| 61 | + /0000 { |
| 62 | + /glob "*" |
| 63 | + /type "deny" |
| 64 | + } |
| 65 | + /0001 { |
| 66 | + /glob "*.html" |
| 67 | + /type "allow" |
| 68 | + } |
| 69 | + } |
| 70 | + /allowedClients { |
| 71 | + ## By default block all IP from allowing to initiate the invalidation commands |
| 72 | + /0000 { |
| 73 | + /glob "*.*.*.*" |
| 74 | + /type "deny" |
| 75 | + } |
| 76 | + ## Allow certain IP's like publishers to invalidate cache |
| 77 | + $include "/etc/httpd/conf.dispatcher.d/cache/ams_publish_invalidate_allowed.any" |
| 78 | + } |
| 79 | + ## Cache response headers next to a cached file. On the first request to |
| 80 | + ## an uncached resource, all headers matching one of the values found here |
| 81 | + ## are stored in a separate file, next to the cache file. On subsequent |
| 82 | + ## requests to the cached resource, the stored headers are added to the |
| 83 | + ## response. |
| 84 | + ## Note, that file globbing characters are not allowed here. |
| 85 | + /headers { |
| 86 | + "Cache-Control" |
| 87 | + "Content-Disposition" |
| 88 | + "Content-Type" |
| 89 | + "Expires" |
| 90 | + "Last-Modified" |
| 91 | + "X-Content-Type-Options" |
| 92 | + } |
| 93 | + ## By default we want to cache every page regardless if it has a query parameter. |
| 94 | + ## For pages that render html differently based on the query parameters |
| 95 | + ## please add entries to deny the caching of those query parameters in this section |
| 96 | + /ignoreUrlParams { |
| 97 | + /0001 { /glob "*" /type "allow" } |
| 98 | + } |
| 99 | + |
| 100 | + # A grace period defines the number of seconds a stale, auto-invalidated |
| 101 | + # resource may still be served from the cache after the last activation |
| 102 | + # occurring. Auto-invalidated resources are invalidated by any activation, |
| 103 | + # when their path matches the /invalidate section above. This setting |
| 104 | + # can be used in a setup, where a batch of activations would otherwise |
| 105 | + # repeatedly invalidate the entire cache. |
| 106 | + /gracePeriod "2" |
| 107 | + |
| 108 | + ## Enable TTL evaluates the response headers from the backend, and if they |
| 109 | + ## contain a Cache-Control max-age or Expires date, an auxiliary, empty file |
| 110 | + ## next to the cache file is created, with modification time equal to the |
| 111 | + ## expiry date. When the cache file is requested past the modification time |
| 112 | + ## it is automatically re-requested from the backend. |
| 113 | + # /enableTTL "1" |
| 114 | + } |
| 115 | +} |
0 commit comments