anchor.diff:  be accepted. `PUT /public/foo` on the other hand, will not match the method permissions of `permit1` and so
   `deny1` will be activated and reject the request.
   
  -### Matching multiple paths and methods: both win
  +=== Matching multiple paths and methods: both win
   
   If multiple permission sets specify the same path and method (or multiple have no method) then both permissions have to
   allow access for the request to proceed. Note that for this to happen both have to either have specified the method, or
  
positive.code: TIP: Given the above permission set, `GET /public/foo` would match both the path and method and thus be allowed,
  whereas `POST /public/foo` would match the path but not the method and would thus be rejected.
  
  ### Matching multiple paths: longest wins
  
  Matching is always done on a longest path basis, less specific permission sets are not considered if a more specific one
  has been matched:
  
negative.code: <5> The `/subject/denied` endpoint disallows any access regardless of whether the call is authenticated by specifying the `@DenyAll` annotation.
  
  
  == Authorization of Web Endpoints using configuration
  
  Quarkus has an integrated plugable web security layer. If security is enabled all HTTP requests will have a permission
  check performed to make sure they are permitted to continue.
  