-
Notifications
You must be signed in to change notification settings - Fork 189
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
Spacenames should be validated/sanitized #4925
Comments
|
For windows we also have: |
Trailing spaces as often provided by mac for filenames are another unrelated huge toppic. |
Ok great. Will do so. Any suggestion for the max length? |
250-255 should work, on mostly any platform but would probably always be trimmed. |
@kulmann please see the full thread. We have the question if ownCloud web could do some client side validation before submitting the Create Space Request. We would prefer not to introduce "automatic" sanitation of the posted data on the server side and prefer server and client side validation of the space name. |
As of now web doesn't validate space names (except for forbidding empty strings), but I'd like to add that. For file- and folder-names there is some basic validation in place, see https://github.com/owncloud/web/blob/3b34cc1e87022dffce176a6cfd6c75f5bb040f3d/packages/web-app-files/src/components/AppBar/CreateAndUpload.vue#L463 (code is ugly and old, but works for now). I can apply whatever validation we agree upon here. @mbarz I told you in a call today, that there is a capability in place, but I remembered that incorrectly. There is a capability for a file extension blacklist in oc10 - that forbids |
for the record, clarified in chat that the linked validation is only for folder names, not for space names. Space name validation is coming in owncloud/web#7890 |
comes with this: #4955 |
fixed |
Right now spacenames are not validated in any way. However having certain characters in a space name can break or heavily influence clients. Proposed sanitization includes:
Still to be decided: Should the server sanitize or return
BAD REQUEST
?The text was updated successfully, but these errors were encountered: