This was due to incorrect parsing of the URI path while
locating a resource in the current tree. The logic to do
this has been changed not to parse the path but to compare
the path to existing resources first and then build those
that do not exist to correctly locate the resource in the tree.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=586169
This was due to incorrect parsing of the URI path while
locating a resource in the current tree. The logic to do
this has been changed not to parse the path but to compare
the path to existing resources first and then build those
that do not exist to correctly locate the resource in the tree.