| Summary: | sending a file with 0 bytes gives always "Failed"as status | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | Toralf Förster <toralf.foerster> |
| Component: | dcc | Assignee: | Bernd Buschinski <b.buschinski> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | konversation-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 1.4 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Toralf Förster
2013-09-05 17:43:17 UTC
Well, is there any good reason so send 0 byte files? I would just consider it as spam, therefor the failed is intented. If you have a VERY good reason for sending 0byte files, feel free to reopen the bug. (In reply to comment #1) > Well, is there any good reason so send 0 byte files? > I would just consider it as spam, therefor the failed is intented. > > If you have a VERY good reason for sending 0byte files, feel free to reopen > the bug. Probbaly you're right- otoh it could be only the file *name* which could be interesting enough. Maybe either b/c it contains character/s which lets act software in an somehow interesting behaviour or b/c of (ok, much more obscure reason) steganographic goals. Well - not strong enough, or ? |