b2stage-gridftp tries to resolve invalid handles

[cookie33]

used b2stage-gridftp with tag 1.8

A list of a directory tries to do following (from the logfile):

[330770] Mon Apr  9 13:57:38 2018 :: irods2.storage.surfsara.nl:36830: [CLIENT]: MLSD /SURFsaraTest03/home/globustest/
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: if '/SURFsaraTest03/home' is a PID the Handle Server 'http://<fqdn>:8003/api/handles' will resolve it!!
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: manage_pid invoked..
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: complete handle URL: http://<fwdn>:8003/api/handles/SURFsaraTest03/home
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: JSON output from the Handle Server: {"responseCode":301,"message":"That prefix doesn't live here","handle":"SURFsaraTest03/home"}
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: JSON responseCode =  301
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: unable to resolve the PID. The Handle Server returned the response code: 301
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: stat_info->pathname=/SURFsaraTest03/home/globustest
[330770] Mon Apr  9 13:57:38 2018 :: iRODS DSI: found collection /SURFsaraTest03/home/globustest.

But a handle always exists of: <prefix>/<suffix>

So it should not try to resolve a bogus handle. This you can easily see because the originating data consists of /SURFsaraTest03/home/globustest/ which contains more than 2 items. So it does not adhere to a handle. So it does not need to be resolved. This should increase the speed and burden the load of the handle sever less with invalid handles.

I hope this makes sense.