Re: Send FTP ABOR Command with TCP Urgent
From: Alun Jones [MSFT] (alunj_at_online.microsoft.com)
Date: 08/04/04
- Next message: Pawar: "Re: Gina API's"
- Previous message: John Phillips: "Re: Socket connection time out"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Aug 2004 09:42:14 -0700
"RepublicOfTaiwan@nospam.nospam"
<RepublicOfTaiwan@nospam.nospam@discussions.microsoft.com> wrote in message
news:7D456B41-000C-4612-AE04-06F283DF7A7E@microsoft.com...
> I am implementing an FTP client, and I would like to send ABOR command
with TCP urgent.
>
> I searched the web and found two kinds of implementations:
> 1. "\377\364", "\377\362" (MSG_OOB), "ABOR\r\n"
> 2. "\377\364\377", "\362" (MSG_OOB), "ABOR\r\n"
>
> MS always does things differently. I sniffed MS FTP client, and found it
uses
> "\000" (MSG_OOB), "\362\377\364ABOR\r\n"
>
> Which is the correct way?
Since MSG_OOB is implemented in at least two different and incompatible
ways, the MSG_OOB flag is mostly a historical nod, rather than something a
client absolutely must do. Try your client operation without MSG_OOB, and
you'll find that there is no problem. Most FTP servers will not even check
for the MSG_OOB, or even for the Synch, IP telnet commands. My advice:
don't worry so hard. Pick one. Read RFC 959, 854 and perhaps 1123, and see
if you can figure out which one you think is correct. For bonus points, see
if you can figure out why other people thought that the others were correct.
[Hint: RFCs are not always consistent, even within themselves. A
two-character sequence, an "interpret as command" escape character, followed
by a command character, is sometimes referred to as a "character", and you
have to guess whether they mean that the IAC is superfluous or whether it
was a typo for "command"].
Programming to RFCs is seldom an exact science. Good luck.
Alun.
~~~~
- Next message: Pawar: "Re: Gina API's"
- Previous message: John Phillips: "Re: Socket connection time out"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
