-
Notifications
You must be signed in to change notification settings - Fork 42
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
[COPY] No error generated when destination file name is too long. #54
Comments
I don't think HTTP code 400 (bad request) is the correct code here. The definition for bad request is
Source: https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1 There is nothing wrong with the syntax, because it depends on the target whether or not the file is correct. On some Unix filesystems, this filename would be perfectly fine. The WebDAV specification doesn't specify a result code for this operation (link). I guess status code 422 (unprocessable entity) might be most appriopriate (possibly wrapped inside a multi-status response). |
Could you add the actual response body that is generated by the 207 (multi-status) return code? |
@ramondeklein
Following is the actual XML response that I'm getting from NWebDAV :
Could you please take a look? |
Error-code 500 (internal server error) is never a good idea. I'll take a look, but it might take a few days. I don't have much time at the moment :-( |
Problem Description
NWebDAV return 207 (Multi-Status) status code when trying to copy a file where destination file name is too long(320 chars).
In case of IIS if you you specify a destination file name greater than 256 characters, it returns 404 error status.
I've check the source code and found following code in CopyHandler, please have a look :
Reproduction Procedure
Try to copy a file where destination file name is greater than 256 characters.
Question
Is this intended behaviors or is it a bug?
The text was updated successfully, but these errors were encountered: