Dispatcher Config Authoring (AMS)
Design minimal, deterministic changes for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM 6.5/AMS, then verify with MCP evidence.
Variant Scope
- This skill is AMS-only.
- Scope is fixed by this skill directory; do not ask the user to choose deployment variant.
MCP Tool Contract
Use only these Dispatcher MCP tools:
validate
lint
sdk
trace_request
inspect_cache
monitor_metrics
tail_logs
Workflow
AMS Config Progress
- [ ] 1) Confirm scope and acceptance criteria; if the repo layout is unclear, normalize it with `repo-layout-workflows.md`
- [ ] 2) Apply AMS 6.5 guardrails for tier routing, variables, flush ACL, and immutable boundaries
- [ ] 3) Decompose target URLs (path/selectors/extension/suffix) and use that model for all URL-based rules—filters, cache rules, etc.—using `/path`, `/selectors`, `/extension`, `/suffix` or aligned globs (not raw `/url`) where applicable; then design complete section-level edits
- [ ] 4) Update config with least-privilege defaults (produce final merged section, not isolated rule snippets)
- [ ] 5) Run static checks: validate -> lint (deep/order-aware when filters changed)
- [ ] 6) Run SDK checks: `sdk({"action":"check-files","config_path":"<dispatcher src path>"})`, `sdk({"action":"diff-baseline","config_path":"<dispatcher src path>"})` as needed
- [ ] 7) Run runtime verification in host-path/log environment
- [ ] 8) Return diff, evidence table, risk/rollback, and citations
Verification Scope Selection
Use the shared references to select the minimum evidence set:
Output Contract
Always include:
- files changed + intent
- exact insertion location and final merged section content for each edited block
- checks executed + evidence
- selected test IDs
- risk/rollback plan
- residual risks and next checks
Feature cross-boundary (Playbook G: auth_checker)
Permission-sensitive caching (/auth_checker) is end-to-end: it requires both Dispatcher config and an AEM servlet. When implementing Playbook G from scratch, create or verify the auth-check servlet in the project core bundle (path /bin/permissioncheck, HEAD/GET, 200 or 403) and allowlist it on publish; then add the /auth_checker block, filter allow for the endpoint, and /allowAuthorized "1" in /cache. See config-scenario-playbooks.md Playbook G and reference-snippets.md.
Guardrails
- Do not weaken deny-by-default security posture without explicit user approval.
- Do not claim runtime verification if host-path/log prerequisites were missing.
- Keep changes minimal and scoped.
References
1---2name: config-authoring3description: Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM 6.5 LTS environments only. Use for `.any`, vhost, rewrite, cache, and filter changes.4license: Apache-2.05compatibility: Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`).6allowed-tools: validate lint sdk trace_request inspect_cache monitor_metrics tail_logs7metadata:8 source: https://skillmd.com/skills/adobe/config-authoring9 mcp-tool-contract: core-7-tools10---1112# Dispatcher Config Authoring (AMS)1314Design minimal, deterministic changes for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM 6.5/AMS, then verify with MCP evidence.1516## Variant Scope1718- This skill is AMS-only.19- Scope is fixed by this skill directory; do not ask the user to choose deployment variant.2021## MCP Tool Contract2223Use only these Dispatcher MCP tools:2425- `validate`26- `lint`27- `sdk`28- `trace_request`29- `inspect_cache`30- `monitor_metrics`31- `tail_logs`3233## Workflow3435```text36AMS Config Progress37- [ ] 1) Confirm scope and acceptance criteria; if the repo layout is unclear, normalize it with `repo-layout-workflows.md`38- [ ] 2) Apply AMS 6.5 guardrails for tier routing, variables, flush ACL, and immutable boundaries39- [ ] 3) Decompose target URLs (path/selectors/extension/suffix) and use that model for all URL-based rules—filters, cache rules, etc.—using `/path`, `/selectors`, `/extension`, `/suffix` or aligned globs (not raw `/url`) where applicable; then design complete section-level edits40- [ ] 4) Update config with least-privilege defaults (produce final merged section, not isolated rule snippets)41- [ ] 5) Run static checks: validate -> lint (deep/order-aware when filters changed)42- [ ] 6) Run SDK checks: `sdk({"action":"check-files","config_path":"<dispatcher src path>"})`, `sdk({"action":"diff-baseline","config_path":"<dispatcher src path>"})` as needed43- [ ] 7) Run runtime verification in host-path/log environment44- [ ] 8) Return diff, evidence table, risk/rollback, and citations45```4647## Verification Scope Selection4849Use the shared references to select the minimum evidence set:5051- [mode-specific-verification-matrix.md](./references/dispatcher-foundation/mode-specific-verification-matrix.md)52- [test-case-catalog.md](./references/dispatcher-foundation/test-case-catalog.md)5354## Output Contract5556Always include:5758- files changed + intent59- exact insertion location and final merged section content for each edited block60- checks executed + evidence61- selected test IDs62- risk/rollback plan63- residual risks and next checks6465## Feature cross-boundary (Playbook G: auth_checker)6667Permission-sensitive caching (`/auth_checker`) is end-to-end: it requires both Dispatcher config and an AEM servlet. When implementing Playbook G from scratch, create or verify the auth-check servlet in the project core bundle (path `/bin/permissioncheck`, HEAD/GET, 200 or 403) and allowlist it on publish; then add the `/auth_checker` block, filter allow for the endpoint, and `/allowAuthorized "1"` in `/cache`. See [config-scenario-playbooks.md](./references/config-authoring/config-scenario-playbooks.md) Playbook G and [reference-snippets.md](./references/config-authoring/reference-snippets.md).6869## Guardrails7071- Do not weaken deny-by-default security posture without explicit user approval.72- Do not claim runtime verification if host-path/log prerequisites were missing.73- Keep changes minimal and scoped.7475## References7677- [config-patterns.md](./references/config-authoring/config-patterns.md)78- [config-scenario-playbooks.md](./references/config-authoring/config-scenario-playbooks.md) – high-value development scenarios adapted from broader MCP surfaces to core-7 execution79- [reference-snippets.md](./references/config-authoring/reference-snippets.md) – reusable starter snippets for consistent config authoring80- [validation-playbook.md](./references/config-authoring/validation-playbook.md)81- [mcp-tool-orchestration.md](./references/config-authoring/mcp-tool-orchestration.md)82- For **runtime prompts** and **troubleshooting scenarios** (tail_logs, trace_request, monitor_metrics, inspect_cache), use the **incident-response** skill reference `runtime-prompts-and-troubleshooting-scenarios.md` when incident triage is needed.83- [quick-start-execution-path.md](./references/dispatcher-foundation/quick-start-execution-path.md) – single entry path for new users and broad requests84- [repo-layout-workflows.md](./references/dispatcher-foundation/repo-layout-workflows.md) – map the user repo to the dispatcher `src` root and likely file families85- [playbook-command-linkage.md](./references/dispatcher-foundation/playbook-command-linkage.md) – convert selected playbooks into exact MCP command chains86- [ams-6-5-guardrails.md](./references/dispatcher-foundation/ams-6-5-guardrails.md)87- [mode-specific-verification-matrix.md](./references/dispatcher-foundation/mode-specific-verification-matrix.md)88- [test-case-catalog.md](./references/dispatcher-foundation/test-case-catalog.md)89- [change-risk-and-rollback-template.md](./references/dispatcher-foundation/change-risk-and-rollback-template.md)90- [public-doc-citation-rules.md](./references/dispatcher-foundation/public-doc-citation-rules.md)91- [public-docs-index.md](./references/dispatcher-foundation/public-docs-index.md)92- [core-7-tools-reference.md](./references/dispatcher-foundation/core-7-tools-reference.md)