Opened 11 years ago

Last modified 9 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: virkony@… Owned by: reimar
Priority: unimportant Component: streaming
Version: unspecified Severity: minor
Keywords: Cc:
Blocked By: Blocking:
Reproduced by developer: Analyzed by developer:

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)

ftpABOR.txt (1020 bytes) - added by virkony@… 11 years ago.
Example of ABOR command with invalid handling of IAC-IP, IAC-DM
stream-tolerance.patch (2.3 KB) - added by virkony@… 11 years ago.
patch to introduce some tolerance in FTP and HTTP streaming

Download all attachments as: .zip

Change History (5)

Changed 11 years ago by virkony@…

Example of ABOR command with invalid handling of IAC-IP, IAC-DM

comment:1 Changed 11 years ago by virkony@…

Changed 11 years ago by virkony@…

patch to introduce some tolerance in FTP and HTTP streaming

comment:2 Changed 11 years ago by virkony@…

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 Changed 9 years ago by compn

  • Owner changed from r_togni@… to reimar
Note: See TracTickets for help on using tickets.