Opened 15 years ago
Last modified 13 years ago
#1361 new defect
Too strict about FTP and HTTP. Failed to seek at ProFTPd. Failed to play when server HTTP gets 206.
| Reported by: | Owned by: | reimar | |
|---|---|---|---|
| Priority: | unimportant | Component: | streaming |
| Version: | unspecified | Severity: | minor |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Reproduced by developer: | no | Analyzed by developer: | no |
Description
Some FTP servers doesn't understand telnet sequences and uses them as prefix for next command (i.e. ABOR).
Some HTTP servers (PHP scripts) sends 206 Partial Content with full range even when there was no Range header in request.
Attachments (2)
Change History (5)
by , 15 years ago
| Attachment: | ftpABOR.txt added |
|---|
comment:1 by , 15 years ago
by , 15 years ago
| Attachment: | stream-tolerance.patch added |
|---|
patch to introduce some tolerance in FTP and HTTP streaming
comment:2 by , 15 years ago
FTP NOOP command just after IAC sequence will save us from next command ignorance (even if NOOP is not supoported)
Most of HTTP 2xx answers should be understood as OK, especially 206. Probably need to do some Range checking, but for my situation is enough to handle it in the same way as 200.
comment:3 by , 13 years ago
| Owner: | changed from to |
|---|
Note:
See TracTickets
for help on using tickets.
Example of ABOR command with invalid handling of IAC-IP, IAC-DM