-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failure with special chars in paths #72
Comments
That should be a good addition; most of the testing I do is under Linux, which doesn't have that limitation. We'll review the list of disallowed characters for folder names that are allowable in URIs and make a list of characters to replace. |
I have encountered at least these three: |
@Flow86 please try out the branch "special-character-handling"; this change should detect the naming restrictions automatically so you do not need to specify anything new on the command line. From the systems I have available and running on Windows, this seems to address the issue. |
Hi, |
Thanks for confirming! It'll likely get merged later today so it's part of the main release. |
We'll also open an issue in the Redfish-Service-Validator to throw a warning if it sees these characters in URIs. While they are "legal" from the RFC and Redfish Specification perspective, they should be discouraged... |
Hi,
I'm using Redfish-Mockup-Creator on windows, trying to read a dell poweredge system. The poweredge system contains paths like
/redfish/v1/Systems/System.Embedded.1/Storage/RAID.Integrated.1-1/Drives/Disk.Bay.7:Enclosure.Internal.0-1:RAID.Integrated.1-1
(note the:
in there!)Writing these files to disk on windows fails.
Is there a way to modify the file downloads to have "safe" filenames? (i.e replace any special char with an underscore)
Thank you
The text was updated successfully, but these errors were encountered: