Either .. This was originally built to be only configurable by osgi properties and the page properties were strapped on the back (as you can see). 

 Wrt to the osgi properties check out `configurePathMap()` .. they mapping can be in 1 of 3 formats -- the "key" entry defines the scope of the value.

```
 if(StringUtils.isBlank(val)) {
      val = key + "/" + DEFAULT_ERROR_PAGE_NAME;
 } else if(StringUtils.equals(val, ".")) {
      val = key;
} else if(!StringUtils.startsWith(val, "/")) {
      val = key + "/" + val;
}

sortedMap.put(key, val);
```

`/content/foo/bar:errors` => results in an error root path of => `/content/foo/bar/errors` for `/content/foo/bar`

`/content/foo/bar:.` => results in an error root path of => `/content/foo/bar` for `/content/foo/bar`

`/content/foo/bar:/content/animals/dog` => results in an error root path of =>` /content/animals/dog` for `/content/foo/bar`

The error pages defined on the pages themselves take precedence over the osgi config if there is a conflict.