Cant honestly see what the problem was...
Passive FTP is a well established mode, and is router/firewall (at the
client) friendly as they only ever make outgoing connections.
The only advantage I can see with this, is that the server side
router/firewall only needs one port forwarded.
Disadvanta
> As above, what's wrong with Passive (or PASIV) mode?
NAT routers at both ends cause problems for any sort of FTP, as do the
random ports used for the data connection.
It may be an outgoing connection from the server, but the incoming
connection may be blocked by the firewall.
Often FTP does
Dave Baxter wrote:
> Mind you, how would you handle simultaneous connections to one port
> anyway...At present, I don't think it's possible without
> alterations
> to everyone's TCP/IP stack? Unless someone knows better.
No problem, the client establishes a second connection to Port
21 and t
Hi All,
Angus and I added UTF-8 support to the TFtpCli V7.
All Delphi versions from D7 to D2009 are supported.
You can download the latest ICS versions from the SVN repositories.
If you don't use a SVN client yet I recommend to give the great
TortoiseSVN a trial. URLs and login infos are availab
Hello,
I think I missed the conversation so need to ask to confirm:
Do you have aplans for UTF-8 TFtpServer? If so, any ETA?
BTW, I recall some Russian and Chinese customers complaining about our
THttpServer based web server as well. Is there any way to support Unicode on
web side as well?
Best
> Do you have aplans for UTF-8 TFtpServer? If so, any ETA?
Much of the low level stuff is done, common with the client, the server
itself will be done in the next week or two, depending on my other
commitments.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please got
> Angus wrote a little HowTo:
I was going to update some of server comments today:
Microsoft FTP7 for IIS/7 for Windows 2008 - fully Unicode capable,
defaults to UTF8 OFF and returns ANSI file listings, OPTS UTF8 or OPTS
UTF8 ON enables UTF8 file listings and uploads.
RhinoSoft Serv-U FTP Server
> Angus and I added UTF-8 support to the TFtpCli V7.
I think Angus and Arno deserve a BIG thank from all of us for the huge work
they've done supporting internationalisation in FTP component.
Thanks guys !
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (
Scrive Maurizio Lotauro <[EMAIL PROTECTED]>:
> Scrive Arno Garrels <[EMAIL PROTECTED]>:
>
> > Maurizio Lotauro wrote:
[...]
> > Looking into THttpCli.SocketDataAvailable, OnDataPush seems to be
> > triggered in this case. LastResponse should the contain 401/407,
> > possibly you handle this ca
Angus Robertson - Magenta Systems Ltd wrote:
>> Do you have aplans for UTF-8 TFtpServer? If so, any ETA?
>
> Much of the low level stuff is done, common with the client, the
> server itself will be done in the next week or two, depending on my
> other commitments.
Should be worth mentioning that
I think it's ok considering Win2000 was launched 9 years ago.
On Fri, Sep 19, 2008 at 3:10 PM, Arno Garrels <[EMAIL PROTECTED]> wrote:
> Angus Robertson - Magenta Systems Ltd wrote:
> >> Do you have aplans for UTF-8 TFtpServer? If so, any ETA?
> >
> > Much of the low level stuff is done, common w
Hmmm...
I still don't see what the problem was this is trying to get round. I
run two FTP servers at different sites, and have never had any
router/firewall problems as they both tell the client to use Passive
mode, so the client only ever makes outgoing connections, and by
default, any router/f
>--- Original Message ---
>From: Maurizio
Lotauro[mailto:[EMAIL PROTECTED]
>Sent: 9/19/2008 8:12:30 AM
>To : twsocket@elists.org
>Cc :
>Subject : RE: Re: [twsocket] Early web server response
>
> How I can avoid the second chunk or tell the server
that I'm starting a new s
> Should be worth mentioning that some of this low level stuff won't
> run on Win9x anymore. If you still need to support Win9x ICSv6 and
> D7-D2007 is the way to go (is this evil?).
There is also the issue of UTF8 support in ICS V6.
My current feeling is it's not worth the effort to support
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
>> Angus and I added UTF-8 support to the TFtpCli V7.
>
> I think Angus and Arno deserve a BIG thank from all of us for the huge
> work
> they've done supporting internationalisation in FTP component.
> Thanks guys !
>
+1
Francois Piette wrote:
>> Angus and I added UTF-8 support to the TFtpCli V7.
>
> I think Angus and Arno deserve a BIG thank from all of us for the huge work
> they've done supporting internationalisation in FTP component.
> Thanks guys !
Yes, it's great to hear that! Thanks for all the work that
Double Ditto! Thanks much... :)
>> From: "Francois Piette" <[EMAIL PROTECTED]>
>> Angus and I added UTF-8 support to the TFtpCli V7.
>
> I think Angus and Arno deserve a BIG thank from all of us for the huge
> work
> they've done supporting internationalisation in FTP component.
> Thanks guys !
Scrive "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
> >--- Original Message ---
> >From: Maurizio
> Lotauro[mailto:[EMAIL PROTECTED]
> >Sent: 9/19/2008 8:12:30 AM
> >To : twsocket@elists.org
> >Cc :
> >Subject : RE: Re: [twsocket] Early web server response
> >
> > How I can
Scrive Arno Garrels <[EMAIL PROTECTED]>:
> Hi All,
>
> Angus and I added UTF-8 support to the TFtpCli V7.
> All Delphi versions from D7 to D2009 are supported.
Well done guys!
Bye, Maurizio.
This mail has been sent using Alpikom webmail s
>--- Original Message ---
>From: Maurizio
Lotauro[mailto:[EMAIL PROTECTED]
>Sent: 9/19/2008 10:25:03 AM
>To : twsocket@elists.org
>Cc :
>Subject : RE: Re: [twsocket] Early web server response
>
> I cannot close the connection, it will not
> work with NTLM authentication.
Scrive "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
> >--- Original Message ---
> >From: Maurizio
> Lotauro[mailto:[EMAIL PROTECTED]
> >Sent: 9/19/2008 10:25:03 AM
> >To : twsocket@elists.org
> >Cc :
> >Subject : RE: Re: [twsocket] Early web server response
> >
> > I cannot
Maurizio Lotauro wrote:
> This will work with Basic bu not with NTLM because (IIRC) the
> authentication phase is started by the server with the first 401.
Looks like sending body data must be delayed somehow, realy not
nice!
Maybe OnSendBegin is the right place:
THttpCli.SocketSessionConnected(
>--- Original Message ---
>From: Maurizio
Lotauro[mailto:[EMAIL PROTECTED]
>Sent: 9/19/2008 11:24:14 AM
>To : twsocket@elists.org
>Cc :
>Subject : RE: Re: [twsocket] Early web server response
>
> This will work with Basic bu not with NTLM because
(IIRC)
> the authenticati
On Fri, Sep 19, 2008 at 7:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >--- Original Message ---
> >From: Maurizio
> Lotauro[mailto:[EMAIL PROTECTED]
> >Sent: 9/19/2008 11:24:14 AM
> >To : twsocket@elists.org
> >Cc :
> >Subject : RE: Re: [twsocket] Early web serv
Thank you. I understand then. That obviously
invalidates my suggestion.
However, I wonder how this works in practice. I
mean, how do regular browsers deal with it? The RFC
specifically states that if you receive an error
after the headers, and you used a Content-Length
header, you MUST (their
Scrive Arno Garrels <[EMAIL PROTECTED]>:
> Maurizio Lotauro wrote:
> > This will work with Basic bu not with NTLM because (IIRC) the
> > authentication phase is started by the server with the first 401.
>
> Looks like sending body data must be delayed somehow, realy not
> nice!
I don't think so,
Scrive "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
[...]
> Again, I must be missing something (I admit I am not
> very familiar with NTLM authentication).
As Fastream already wrote, the server send a (sort of?) token with the 401
answer. You car read more info there:
http://davenport.sourceforge.n
Scrive "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
[...]
> However, I wonder how this works in practice. I
> mean, how do regular browsers deal with it?
Good question. Someone that know the html can prepare a page with a text box
where write the content to send and a post button?
It will be very u
28 matches
Mail list logo
