Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.6.0
-
None
Description
Right now FilterFs and ChRootedFs pass the following up to the AbstractFileSystem superconstructor:
super(fs.getUri(), fs.getUri().getScheme(), fs.getUri().getAuthority() != null, fs.getUriDefaultPort());
This passes a value of authorityNeeded==true for any fs which has an authority, but this isn't necessarily the case - ViewFS is an example of this. You will encounter this issue if you try to filter a ViewFS, or nest one ViewFS within another. The authorityNeeded check isn't necessary in this case anyway; fs is already an instantiated AbstractFileSystem which means it has already used the same constructor with the value of authorityNeeded (and corresponding validation) that it actually requires.