Peter Van Hove wrote:
>>> Should I URL encode the POST data as well ?
>>
>> Yes.
>
> I did ... it did not help.
> I used your older URLEncode() function that has UTF-8 conversion hard
> coded in it (I could not check out the newer version, see other
> email).
>
> I came to the conclusion that t
> The SVN HTTP version does seem to be showing revision 297 which is 10
> days old, I'll see if the server has stopped or something.
>
> You should really be using proper SVN or TortoiseSVN, which will show a
> much later revision including the units Arno checked in this morning.
> //
> Do you us
Peter Van Hove wrote:
>> While writing this, I think I introduced a bug in function
>> UrlEncode which always converted to UTF-8 in V7.
>> I just checked in a change, both UrlEncode and UrlDecode take a
>> CodePage argument now.
>
>>
>> Yes now there is ;-), update your local work copy and use Ur
> I tried to update but no files were changed.
> Still "Completed: At revision: 297"
> Did you really check in ?
The SVN HTTP version does seem to be showing revision 297 which is 10
days old, I'll see if the server has stopped or something.
You should really be using proper SVN or TortoiseSVN, w
>> Should I URL encode the POST data as well ?
>
> Yes.
I did ... it did not help.
I used your older URLEncode() function that has UTF-8 conversion hard coded
in it (I could not check out the newer version, see other email).
I came to the conclusion that the '=' sign cannot be encoded as then it
> While writing this, I think I introduced a bug in function
> UrlEncode which always converted to UTF-8 in V7.
> I just checked in a change, both UrlEncode and UrlDecode take a
> CodePage argument now.
>
> Yes now there is ;-), update your local work copy and use UrlEncode()
> located in uni
Peter Van Hove wrote:
>>> Interesting !!!
>>> So POST and GET data, when sent to a host, are not unicode ?
>>
>> They are not sent as UTF-16 Unicode, correct.
>>
>>> And so what I provide to the component when I do a GET, in unicode,
>>> is converted in the component to something else (UTF 8 ?)
>
[twsocket] THttpCli POST issue with v7 Commit 317
>I just converted a piece of code to CB2009 (coming from BCB5), not
> originally written by myself, so it's a bit searching what is what, but I
> believe I run into a component issue. Meanwhile I created the same app in
> BCB5 a
>> Interesting !!!
>> So POST and GET data, when sent to a host, are not unicode ?
>
> They are not sent as UTF-16 Unicode, correct.
>
>> And so what I provide to the component when I do a GET, in unicode, is
>> converted in the component to something else (UTF 8 ?)
>
> Yes, in V7 a GET request is
>>> The Problem:
>>> On the receiving end (webpage) the the POST variable doesn't arrive
>>> intact. Only the first letter. In this example case only "t" arrives
>>> (so "t = test" instead of "test = test"
>>> As suggested, the value arrives intact (in this case "test")
>
>> It's no bug. The compo
Arno Garrels wrote:
> With POST requests however the send stream is sent as is and the
> component user is responsible to format and encode the stream content
> properly. Posted data may, for example, contain multple parts all with
> a different Charset and Content-Transfer-Encoding part-header.
T
Peter Van Hove wrote:
>>> The Problem:
>>> On the receiving end (webpage) the the POST variable doesn't arrive
>>> intact. Only the first letter. In this example case only "t"
>>> arrives (so "t = test" instead of "test = test"
>>> As suggested, the value arrives intact (in this case "test")
>
>>
>> The Problem:
>> On the receiving end (webpage) the the POST variable doesn't arrive
>> intact. Only the first letter. In this example case only "t" arrives
>> (so "t = test" instead of "test = test"
>> As suggested, the value arrives intact (in this case "test")
> It's no bug. The component us
Peter Van Hove wrote:
> Can somebody confirm, possibly fix if it's an issue ?
It's no bug. The component user is responsible to format
posted data properly.
>
> The Problem:
> On the receiving end (webpage) the the POST variable doesn't arrive
> intact. Only the first letter. In this example
I just converted a piece of code to CB2009 (coming from BCB5), not
originally written by myself, so it's a bit searching what is what, but I
believe I run into a component issue. Meanwhile I created the same app in
BCB5 and there is works OK, using the same code.
I used HEAD version v7, checke
15 matches
Mail list logo
