anchor.diff:  
   ACL allows to protect your API's (or proxy `upstreams`) by a scope-based authorization.
   
  -Once enabled it will read `scopes` from any authentification plugin (eg. `JWT`). If there are no scopes, it will send responses with `unathorized` status.
  +Once enabled it will read `scopes` from any authorization plugin (eg. `JWT`). If there are no scopes, it will send responses with `unathorized` status.
   
   If path is not defined (gateway can not extract list of scopes needed for path), unathorized response is sent.
   
  
positive.code: 
  But if token is invalid, appropriate error response will be send back to api consumer.
  
  ## JWT Authentification [/apis/{api_id}/plugins/jwt]
  
  ### General Information
  JWT is a authroization plugin that decodes JWT tokens received from api consumer (with a `signature` field that is set in settings) and extacts `scopes` field from it.
  
negative.code: 
  ### `Plugin_Proxy__Settings`
  + upstream (Plugin_Proxy__Settings__Upstream, fixed-type)
  + `strip_host`: false (boolean, optional) - Keep HTTP HOST host header when proxying request to an upstream.
  + `strip_request_path`: false (boolean, optional) - Strip API part of path when sending request to upstream. 
  
  ### `Plugin_Proxy__Settings__Upstream`
  + scheme: https (string) - HTTP request scheme. May be: `http`, `https`, `amqp`, `ws`.
  + host: binlist.net (string) - DNS address of your upstream or its IP.
  + port: 443 (number) - Port on which your upstream recieves requests.
  