Hi,
Then how come Mozilla Firefox doesn´t have this weird char problem? I
just used a TMemoryStream instead of using my old TStringStream, debugged
the contents of the Buffer and it is as buggy as it was.
How come the server is sending me something and the browser something
else? :'( Because I trully don't believe that Mozilla Firefox is parsing
that kind of data. It even doesn't respect the same amount of bytes per char
...). I don't get it.. Me stupid!!! 8/
Thank you for your time,
Marcelo Grossi
----- Original Message -----
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Thursday, July 20, 2006 4:24 PM
Subject: Re: [twsocket] HttpCli UTF-8 Coding Issue
>> How do I get the chance of interpreting the characters with HttpCli? I
>> don't set any property whatsoever regarding the enconding of the data I'm
>> receiving. The TStringStream the data comes is already the way I showed
>> in
>> my last message ... How do I get the "raw" data or something?
>
> With HTTP component, you always get the data exactly as the server sent
> it.
> HTTP component does do any processing on the data itself. It is stored as
> is
> in the stream you provide for storage.
>
> Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
> --
> [EMAIL PROTECTED]
> http://www.overbyte.be
>
>
> --
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
