-
Notifications
You must be signed in to change notification settings - Fork 120
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
/ as first symbol #11
Labels
pending
Not looking at it yet
Comments
Hmm. Perhaps not by default, but with some option to the server to be more tolerant. Don't forget that / is only special on Unix. |
I'm assuming that this is in the sample client? It can't be in the api or you'd just fix it yourself in what you pass in. |
no, that is not sample client. that is client on Linksys spa2102 and Audiocodes mp-202. |
ghost
assigned msoulier
Aug 26, 2011
Taking for 0.7. |
UnwashedMeme
pushed a commit
to UnwashedMeme/tftpy
that referenced
this issue
Nov 1, 2013
Some devices, when uploading, always have a leading '/' that led to the joined path being outside the server's root directory causing "bad file path" TftpExceptions. The only way to work around this is if the remote client knew the full path on this server (unnecessarily tight coupling). This patch removes the leading '/' so that all paths are relative to the server's root directory. To help preserve backwards compatibility there is an exception to the above rule that if the client's specified path starts with the server's root directory then accept it.
probably that issue should be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
it will be great if slash in the beginning of filename will be ignored and don't raises TftpException
i try to get file from tftpy my device got command get -u tftp://$ip:$port/filename and sends /filename as a file to get. unfortunately i can't control that behavior
The text was updated successfully, but these errors were encountered: