|
|
Ian Schneider created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.6.1, 2.6.0 |
|
Assignee: |
|
|
Created: |
29/Dec/14 2:30 PM |
|
Priority: |
|
|
Reporter: |
Major|
Prior to 2.6, GeoServer allowed colons in style and other names as long as the underlying filesystem supported them. The org.geoserver.platform.resource.Paths class checks a regular expression for path validity but does not consider the file system. It seems like using new File(test).getCanonicalPath() will raise an exception on filesystem specific invalid names. This specifically impacts at least one organization that is using a double colon notation and is unable to update. |
|
|
|
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |
|
|
