Currently, get performs globbing of the filename portion in all cases (even when given a fully qualified file path).
This isn't a problem normally (though it may be somewhat inefficient) but in edge cases where the connecting user has permission to read the file, but not its enclosing directory, they encounter errors due to our attempts to listdir during the glob attempt.
I haven't looked closely but I presume we can simply test for "is this path a file?" and short circuit around globbing if that is the case; it would fix the edge case and be that much more efficient the rest of the time.
Credit to Sassa Nf (aka Alex) as per an email thread.
Currently,
getperforms globbing of the filename portion in all cases (even when given a fully qualified file path).This isn't a problem normally (though it may be somewhat inefficient) but in edge cases where the connecting user has permission to read the file, but not its enclosing directory, they encounter errors due to our attempts to
listdirduring the glob attempt.I haven't looked closely but I presume we can simply test for "is this path a file?" and short circuit around globbing if that is the case; it would fix the edge case and be that much more efficient the rest of the time.
Credit to Sassa Nf (aka Alex) as per an email thread.