anchor.diff:  |===
   
   WARNING: `{#request.content}` is only available for policies bound to an `on-request-content` phase.
  +
  +Accessing specific element of the content payload, you can use the JsonPath for example :
  +`{#jsonPath(#request.content, "level.level-1.value")}`
   
   === SSL Object
   The properties you can access in SSL Session object are listed below.
  
positive.code: .^|pathInfo      |Path info              ^.^|string          |/store/MyStore
  .^|pathInfos     |Path info parts        ^.^|array of string |[,store,MyStore]
  .^|contextPath   |Context path           ^.^|string          |/v2/
  .^|params        |Query parameters       ^.^|key / value     |order -> 100
  .^|pathParams    |Path parameters        ^.^|key / value     |storeId -> MyStore (__see Warning for details__)
  .^|headers       |Headers                ^.^|key / value     |X-Custom -> myvalue
  .^|method        |HTTP method            ^.^|string          |GET
  .^|scheme        |HTTP scheme            ^.^|string          |http
  .^|version       |HTTP version           ^.^|string          |HTTP_1_1
  
negative.code: == API
  === Properties
  
  As an API publisher, you can define link:{{ 'apim/3.x/apim_publisherguide_api_properties.html' | relative_url }}[properties]  for your API. These properties are
  automatically _injected_ into the expression language context to be used later.
  
  ==== Example
  
  * Get the value of the property `my-property` defined in API properties:
  `{#properties['my-property']}`
  * Get the value of the property `my-secret` defined and encrypted link:{{ 'apim/3.x/apim_publisherguide_api_properties.html' | relative_url }}[encryption] in API Properties : `{#properties['my-secret'}` to pass a secured property to your backend
  
  === Dictionaries
  
  link:{{ 'apim/3.x/apim_installguide_configuration_dictionaries.html' | relative_url }}[Dictionaries] work in a similar way to properties, but you need to specify the dictionary name as well as the property name.
  
  ==== Example
  
  