anchor.diff:  The `:origin` key can be a set of possible origins or directlly `"*"` for allow all origins.
   
   
  -=== Context as Request
  -
  -By default, the _catacumba_'s context allows you direct access to the request and response, that are
  -instances of classes defined in Ratpack. That classes allows you access to all related properties
  -such as headers, the request body, the request method, etc.
  -
  -But _catacumba_ at this moment offers a very limited set of helper functions for interacting with that
  -data: get/set headers and read the body (explained in previous sections).
  -
  -For compensate this, _catacumba_ comes with special chain handler that populates the context with
  -basic request properties such as, headers, path and method:
  -
  -[source, clojure]
  -----
  -(require '[catacumba.handlers :refer [basic-request]])
  -
  -(def app
  -  (ct/routes [[:prefix "api/v1"
  -               [:any basic-request]
  -               [:get "foo" some-handler]
  -               [:post "foo" some-save-handler]]]))
  -----
  -
  -
  -=== Security
  -
   ==== Content Security Policy
   
   Is a security related chain handler that appropiatelly set the `Content-Security-Policy` headers.
  
positive.code: NOTE: Obviously, if you are using the ring type of hanlder, you can use prone as is, without any
  additional adaptation. This example shows how it can be used with default hanlder type.
  
  
  === Multiuser chat with SSE
  
  This example tries to demostrate how can you build a simple chat using "Server-Sent Events" for
  
negative.code: java -Dcatacumba.port=8000 -Dcatacumba.debug=false -jar yourjarhere.jar
  ----
  
  [[examples]]
  == Examples
  
  === Debugging with prone
  