Can somebody confirm that characters above #127 have to be
encoded UTF-8 first before they are percent-encoded?
If that's correct, Url.pas was and is currently buggy.
When I use IE to get the url http://www.myhost.com/Fête (note the lowercase
e with circumflex), it sends GET /F%C3%AAte to the
I would suggest you contact Primoz which seem to not read the mailing list
curently.
His email is primoz at gabrijelcic dot org
--
[EMAIL PROTECTED]
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
-
Arno Garrels wrote:
jlist wrote:
What I want to do is to avoid providing the two .pem files as
separate files. Instead, I'd like to read the content of the two
files and hard-code them in a string variable, or in resource.
Private Key and certificate may exist in the same file.
It's not a
I'm already on line with Stanislav. He made some changes to my old proxy
unit (I sent him a latest non-public revision - under NDA so don't ask him
for it, please) and he merged most of the changes. The result is not working
yet, as I haven't yet have time to look at the merged version...
Primoz
Francois PIETTE wrote:
Can somebody confirm that characters above #127 have to be
encoded UTF-8 first before they are percent-encoded?
If that's correct, Url.pas was and is currently buggy.
When I use IE to get the url http://www.myhost.com/Fête (note the
lowercase e with circumflex), it
On Sep 27, 2008, at 12:14, Arno Garrels wrote:
Can somebody confirm that characters above #127 have to be
encoded UTF-8 first before they are percent-encoded?
If that's correct, Url.pas was and is currently buggy.
I can't find anything specific on the HTTP and URI RFCs regarding this
DZ-Jay wrote:
I've seen UTF-8 used all the time (and that's what I've used, too),
and in fact that's probably what IE uses--but I can't find it anywhere
specified as the HTTP protocol character set--unless I'm missing
something. It may be that UTF-8, by convention or tradition, is the
de
I can confirm both browsers also translate non-ansi Turkish chars as
unicode:
ğ = %C4%9F
This is soft g, specific to Turkish on all languages.
Regards,
SZ
On Sun, Sep 28, 2008 at 4:49 PM, Arno Garrels [EMAIL PROTECTED] wrote:
DZ-Jay wrote:
I've seen UTF-8 used all the time (and that's what
On Sep 28, 2008, at 09:49, Arno Garrels wrote:
It doesn't seem to be mandatory, however suggested to use UTF-8 since
January 2005, RFC 3986
Thank you! For some reason I missed that 3986 obsoletes 2396.
dZ.
--
DZ-Jay [TeamICS]
DZ-Jay wrote:
On Sep 28, 2008, at 09:49, Arno Garrels wrote:
It doesn't seem to be mandatory, however suggested to use UTF-8 since
January 2005, RFC 3986
Thank you! For some reason I missed that 3986 obsoletes 2396.
If you are interested, I just checked in my UTF-8 changes (v7).
The
Thanks Arno, for the example. I'll give it a try.
Private Key and certificate may exist in the same file.
It's not a method in TX509Base, however you can derive your
own class and add this functionality. Something like below
should do the trick:
--
To unsubscribe or change your settings
11 matches
Mail list logo
