silverstripe-framework/_config/requestprocessors.yml

---
Name: requestprocessors
---
SilverStripe\Core\Injector\Injector:
  SilverStripe\Control\Director:
    properties:
      Middlewares:
        TrustedProxyMiddleware: '%$SilverStripe\Control\Middleware\TrustedProxyMiddleware'
        AllowedHostsMiddleware: '%$SilverStripe\Control\Middleware\AllowedHostsMiddleware'
        SessionMiddleware: '%$SilverStripe\Control\Middleware\SessionMiddleware'
        RequestProcessorMiddleware: '%$SilverStripe\Control\RequestProcessor'
        FlushMiddleware: '%$SilverStripe\Control\Middleware\FlushMiddleware'
  SilverStripe\Control\AllowedHostsMiddleware:
    properties:
      AllowedHosts: "`SS_ALLOWED_HOSTS`"
  SilverStripe\Control\TrustedProxyMiddleware:
    properties:
      TrustedProxyIPs: "`SS_TRUSTED_PROXY_IPS`"
FIX: Move stage choosing into a pre-request filter. This ensures that the correct stage is selected, even if the request does not come through the model as controller system. This fixes an issue where custom controllers would always be on the "Stage" stage. 2013-10-03 16:20:32 +02:00			`---`
			`Name: requestprocessors`
			`---`
NEW: Moved allowed-hosts checking to a middleware. 2017-06-23 05:08:08 +02:00			`SilverStripe\Core\Injector\Injector:`
API: Director::handleRequest() is no longer static - use a Director service NEW: Add HTMLMiddlewareAware trait to HTTPApplication, Director, and RequestHandler NEW: Allow service specs to be passed to Director rules. This refactor of the controller middlewares takes a service definition approach rather than a static-method-and-config approach that Director historically had. The use of a trait for middleware means that the Middlewares array property can be defined on RequestHandler, Director, and HTTPApplication objects in the same way. 2017-06-25 08:03:03 +02:00			`SilverStripe\Control\Director:`
			`properties:`
			`Middlewares:`
FIX Deprecated yml syntax 2017-07-21 12:17:18 +02:00			`TrustedProxyMiddleware: '%$SilverStripe\Control\Middleware\TrustedProxyMiddleware'`
			`AllowedHostsMiddleware: '%$SilverStripe\Control\Middleware\AllowedHostsMiddleware'`
			`SessionMiddleware: '%$SilverStripe\Control\Middleware\SessionMiddleware'`
			`RequestProcessorMiddleware: '%$SilverStripe\Control\RequestProcessor'`
			`FlushMiddleware: '%$SilverStripe\Control\Middleware\FlushMiddleware'`
NEW: Moved allowed-hosts checking to a middleware. 2017-06-23 05:08:08 +02:00			`SilverStripe\Control\AllowedHostsMiddleware:`
			`properties:`
			AllowedHosts: "`SS_ALLOWED_HOSTS`"
NEW: Add TrustedProxyMiddleware API: SS_TRUSTED_PROXY_HOST_HEADER replace with middleware config API: SS_TRUSTED_PROXY_PROTOCOL_HEADER replace with middleware config API: SS_TRUSTED_PROXY_IP_HEADER replace with middleware config API: Front-End-Https = “on” header no longer supported This middleware replaces the TRUSTED_PROXY setting and shifts its configuration out of the env vars and bootstrap and into the Director flow. 2017-06-23 07:28:04 +02:00			`SilverStripe\Control\TrustedProxyMiddleware:`
			`properties:`
			TrustedProxyIPs: "`SS_TRUSTED_PROXY_IPS`"