Paul wrote:
> It's mostly ascii characters, but sometimes, the string contains a few
> unicode characters which can have different code pages for each
> character. Since the ClientCnx.AnswerString is an AnsiString anyway,
> I think the only choise is to convert them to UTF8.
That's correct, howe
> I don't think so, the content-type charset header describes the
> character encoding.
It's mostly ascii characters, but sometimes, the string contains a few
unicode characters which can have different code pages for each character.
Since the ClientCnx.AnswerString is an AnsiString anyway, I thi
I thought it defaulted to PASV, but I'll try it.
--- On Fri, 1/9/09, Arno Garrels wrote:
> From: Arno Garrels
> Subject: Re: [twsocket] Problem FTP with SSL
> To: "ICS support mailing"
> Date: Friday, January 9, 2009, 10:48 AM
> Eddie Shipman wrote:
> > I took the SSLFTPCli demo application a
Paul wrote:
> Are unicode characters in the body part not conform the RFC then ?
Unicode is IMHO valid, it depends on the content-type charset.
Should be "utf-16" for UnicodecodeString.
But in the wild I never saw a utf-16 header so far, probably since it's
a wast of bandwith sending double byte c
Are unicode characters in the body part not conform the RFC then ?
If not, then everything needs to be UTF8 encoded before sending
Paul
- Original Message -
From: "Arno Garrels"
To: "ICS support mailing"
Sent: Friday, January 09, 2009 5:48 PM
Subject: Re: [twsocket] ClientCnx.AnswerS
Paul wrote:
>> an AnsiString on the client side to read it the reply from the
>> server. The server is compiled with D2009.
Yes currently it takes a String and converts it to AnsiString with default
code page in D2009 before sent, see Classes TStringStream.Create(const AString:
string).
Most l
Eddie Shipman wrote:
> I took the SSLFTPCli demo application and set everything up.
>
> However, everything works but the client gets no responses when I do
> a LIST or STOR.
>
> WS_FTP Pro works perfectly, straight out of the box when I set the
> Trusted sites.
It probably uses passive mode or
I took the SSLFTPCli demo application and set everything up.
However, everything works but the client gets no responses when I do a LIST or
STOR.
WS_FTP Pro works perfectly, straight out of the box when I set the Trusted
sites.
Any ideas as to why this may be happening?
The vendor says it may
Forgot to add : it's sent in the body part of ClientCnx.AnswerString on the
server
Paul
- Original Message -
From: "Paul"
To: "TWsocket"
Sent: Friday, January 09, 2009 3:26 PM
Subject: [twsocket] ClientCnx.AnswerString
> Is this still an AnsiString (httpCli) ?
> I'm converting a fe
Is this still an AnsiString (httpCli) ?
I'm converting a few applications to D2009, but it seems I still have to use
an AnsiString on the client side to read it the reply from the server.
The server is compiled with D2009.
regards,
Paul
--
To unsubscribe or change your settings for TWSocket m
10 matches
Mail list logo
