FTP/SFTP: report malformed cap at login instead of use-time #1965
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1965
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I was experimenting with the SFTP server and I accidentally pasted a malformed (truncated) cap into the config. It reports this reasonably well when I try to use it:
(Actually that's not a great error message — it should tell me that this is a malformed cap, not a cap of an unknown type — but that's the topic of a different ticket.)
It would be better if it reported this error as soon as I login rather than waiting until I try to "ls" something.
The issue of reporting invalid cap URIs as if they were unknown, is #1112. (That ticket currently describes the issue only for the CLI, but it's the same underlying problem.)
FTP/SFTP/FUSE: report malformed cap at login instead of use-timeto FTP/SFTP: report malformed cap at login instead of use-timeThe gateway could report the invalid URI at start-up time as well as at login.
Replying to daira:
Good idea, thanks! And thanks for the link to #1112.