Wt

This is related to #11497. But instead of finding a solution to it, we ought to simply document better what happens here.

In case of a --resources-dir being specified, the request to host/resources/... will fall back to this specified directory, instead of looking in docroot/resources.
This does mean that the resources part of the URL will always exist, and always be used as such. No actual 302 is sent, the server handles this itself.

In case of specifying docroot subpaths (i.e. docroot;/path1,/path2) the /resources subpath should ALWAYS be present. Otherwise it is NOT detected that /resources is a static path.

Either we document this better, having a caveat visible in both the section for docroot, as well as resources-dir.
Alternatively, we can ensure that /resources is ALWAYS handled statically, and also document this specific behavior.