Hi Alan,
thanks for your reply.
In fact, I also addressed the issue already in the Cyberduck Github (
issue #15674), but so far there was also no reply.
In our iRODS implementations, users can create links to other iRODS locations, and this is also oftenly used by some of other users. As also a lot of these users, usually those connection from Windows machines, use Cyberduck for data transfer to/from the system, it would be of course good if these links also work properly in Cyberduck.
On the other hand, we saw that if Cyberduck is configured via WebDAV access to our iRODS instance, the links are properly displayed. So this is the current workaround that we have in place for such cases.
Moreover, I would like to emphasize that in the web interface that we provide also for access to the system, these iRODS links work and following them displays the content of the target directory. In the web implementation we also use Jargon for that which is also used by Cyberduck as far as I know.