[JBoss JIRA] Created: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
1:57 a.m.
FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: UncPathTest.java
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:57 a.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
James Livingston updated JBVFS-160:
-----------------------------------
Attachment: UncPathTest.java
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: UncPathTest.java
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:08 a.m.
New subject: [JBoss JIRA] Commented: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
James Livingston commented on JBVFS-160:
----------------------------------------
In particular, the way it converts the URI to a path then back to a URI doesn't work
because (on Windows at least):
new URI("file:////127.0.0.1/shared/").getPath() ==
"//127.0.0.1/shared/"
new URI("file", null, "//127.0.0.1/shared/", null) ==
"file://127.0.0.1/shared"
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: UncPathTest.java
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 a.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
James Livingston updated JBVFS-160:
-----------------------------------
Attachment: JBVFS-160.diff
Okay, this definitely seems to be a JRE bug. The JavaDoc for URI states that:
"For any URI u that does not contain redundant syntax such as two slashes before an
empty authority (as in file:///tmp/ )
...
new URI(u.getScheme(),
u.getUserInfo(), u.getAuthority(),
u.getPath(), u.getQuery(),
u.getFragment())
.equals(u)
if u is hierarchical"
and this doesn't hold for u=new File("\\\\localhost\shared").toURI().
It's possible to work around this by using file.toURL().toURI() instead, and changing
line 132 of FileSystemContext.getFileURI(File file) to be "URL url =
file.toURI().toURL();", which makes having "file:////..." in
conf/bootstrap/profile.xml's applicationURIs work.
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: JBVFS-160.diff, UncPathTest.java
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 p.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
James Livingston updated JBVFS-160:
-----------------------------------
Attachment: (was: JBVFS-160.diff)
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: UncPathTest.java, vfs-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 p.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
James Livingston updated JBVFS-160:
-----------------------------------
Attachment: vfs-unc.diff
Following discussion about how file: URIs should work, it seems best if
FileSystemContext.getFileURI() does the same thing as the JRE's File.toURI()
explicitly adding two more slashes if the path starts with a double slash.
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: UncPathTest.java, vfs-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 p.m.
New subject: [JBoss JIRA] Commented: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on JBVFS-160:
-----------------------------------
I'd just like to note that VFS 3.x does have proper UNC handling; Jason Greene spent a
lot of time researching it and getting it right.
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: John Bailey
Attachments: UncPathTest.java, vfs-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
Ales Justin reassigned JBVFS-160:
---------------------------------
Assignee: Ales Justin (was: John Bailey)
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: Ales Justin
Attachments: UncPathTest.java, vfs-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:23 p.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
James Livingston updated JBVFS-160:
-----------------------------------
Attachment: vfs-uri-unc.diff
Slightly better patch following discussion about where to put this. Passing the empty
string (rather than null) causes the URI constructor to add the two slashes.
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: Ales Justin
Attachments: UncPathTest.java, vfs-unc.diff, vfs-uri-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:51 a.m.
New subject: [JBoss JIRA] Commented: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
Ales Justin commented on JBVFS-160:
-----------------------------------
I've already applied this to 2.2 branch, and just about to do it for 2.1.
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1
Environment: Windows
Reporter: James Livingston
Assignee: Ales Justin
Attachments: UncPathTest.java, vfs-unc.diff, vfs-uri-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:32 a.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://jira.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin.sy...
]
Ales Justin updated JBVFS-160:
------------------------------
Fix Version/s: 2.1.3.SP2
2.2.0.Alpha3
Affects Version/s: 2.2.0.Alpha2
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://jira.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1, 2.2.0.Alpha2
Environment: Windows
Reporter: James Livingston
Assignee: Ales Justin
Fix For: 2.1.3.SP2, 2.2.0.Alpha3
Attachments: UncPathTest.java, vfs-unc.diff, vfs-uri-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 p.m.
New subject: [JBoss JIRA] Resolved: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://issues.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin....
]
James Livingston resolved JBVFS-160.
------------------------------------
Resolution: Done
The fix was committed a while back, but it looks like we forgot to close the JIRA
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://issues.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1, 2.2.0.Alpha2
Environment: Windows
Reporter: James Livingston
Assignee: Ales Justin
Fix For: 2.2.0.Alpha3, 2.1.4.GA
Attachments: UncPathTest.java, vfs-unc.diff, vfs-uri-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 p.m.
New subject: [JBoss JIRA] Updated: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows
[
https://issues.jboss.org/browse/JBVFS-160?page=com.atlassian.jira.plugin....
]
Ales Justin updated JBVFS-160:
------------------------------
Fix Version/s: 2.2.0.SP1
(was: 2.2.0.Alpha3)
FileSystemContext.getFileURI returns wrong URI for UNC paths on
Windows
-----------------------------------------------------------------------
Key: JBVFS-160
URL: https://issues.jboss.org/browse/JBVFS-160
Project: JBoss VFS
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.1.3.SP1, 2.2.0.Alpha2
Environment: Windows
Reporter: James Livingston
Assignee: Ales Justin
Fix For: 2.1.4.GA, 2.2.0.SP1
Attachments: UncPathTest.java, vfs-unc.diff, vfs-uri-unc.diff
When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared),
FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared"
(which is what Windows itself uses) rather than "file:////127.0.0.1/shared"
(which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy
things if they are located on an unmapped UNC location.
I'm attaching a test case for this. To use it, you need to run it on a Windows system
and have access to a something with a UNC path. The code as written expects there to be a
SMB share called "shared" on the machine it is run on, but it can easily be
change to point elsewhere.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4841
days inactive
5244
days old
12 comments
3 participants
participants (3)
-
Ales Justin (JIRA) -
David Lloyd (JIRA)
-
James Livingston (JIRA)