[AMS][2.6-20]

[calebpryor]

Updating the archetype to match what is being built out and distributed as an RPM package ams-dispatcher-configuration-2.6-20 to help avoid confusion

Description

AMS developed default dispatcher configuration files are behind in the archetype.

Related Issue

AMS distributes their updates via OS patches. Changes that are in the ams-dispatcher-configuration package aren't reflected in the archetype and causing confusion.

Motivation and Context

To eliminate the confusion I am attempting to reconcile the archetype source of AMS with the actual installed version files on AMS built systems.

How Has This Been Tested?

Internal Adobe Jenkins jobs have been run against these changes to verify functionality and been rolled out to AMS and a quarterly patch operation

Types of changes

Release 2.6-20

Bug Fixes:

• Updated catch-all and flush farms to pass DOT tests
• AMS Author farm had ignore url params set to allow instead of deny
• Built in farm files have /statfileslevel "{DEFAULT_STAT_LEVEL}" when it should have been /statfileslevel "${DEFAULT_STAT_LEVEL}"
• Adding missing variables in /etc/httpd/conf.d/variables/ams_default.vars for people who upgraded and had modified this file.
• Changed default statfilelevel from 2 to 4
• Changed the names of the farm files to load correctly.
• Removed greedy author-* from default author farm.

New Features:

• New publish filters in /etc/httpd/conf.dispatcher.d/filters/ams_publish_filters.any
• Added ENV_TYPE and RUNMODE into out of the box environment variables
• Added author flush vhost.
• Added default variable init files and mechanism to override defaults.
• Added catch all farm
• Added flush farms
• Changed logformat.conf to display client IP.
• Added Default IgnoreURL Params to be allow all.
• Added Default Flush Grace Period.
• Moved variable includes out of dispatcher_vhost.conf

Security Fixes:

• Deny caching of sensitive data endpoints

Breaking Changes:

• Authorization header was removed from the publish farms. Typically published websites shouldn't accept authenticated people and people who do use authentication on their published site they'll need to add this to their farm Suffixes and Selectors blocked by default. Customers who use selectors and suffixes on their website will need to add to their farm files their specific allow rules to allow the ones they use through.
• Added Default Filter to block suffix and selectors.

Checklist:

• [X] I have signed the Adobe Open Source CLA.
• [X] My code follows the code style of this project.
• [X] My change requires a change to the documentation.
• [X] I have updated the documentation accordingly.
• [X] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.