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).
T
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]
http://www.overbyte.be/eng/overbyte/te
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
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
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
spec
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
> 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
I am not sure of a 100% covering test scenario. Our server is now free, why
don't you test it yourself? (http://www.fastream.com/iqwebftpserver.php)
Regards,
Gorkem
On Sat, Sep 27, 2008 at 7:38 PM, Arno Garrels <[EMAIL PROTECTED]> wrote:
> Fastream Technologies wrote:
> > I think this bug could
Fastream Technologies wrote:
> I think this bug could be a reason why our web server customers have
> been getting complained with html file manipulation in non-ansi...
Can you confirm that it's a bug?
--
Arno Garrels
>
> On Sat, Sep 27, 2008 at 7:14 PM, Arno Garrels <[EMAIL PROTECTED]>
> wrote
Arno Garrels wrote:
> Hi,
>
> 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.
Same or similar functions are used in the HTTP server.
I have a fix for OverbyteIcsUrl.pas but w
I think this bug could be a reason why our web server customers have been
getting complained with html file manipulation in non-ansi...
On Sat, Sep 27, 2008 at 7:14 PM, Arno Garrels <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Can somebody confirm that characters above #127 have to be
> encoded UTF-8 fir
Hi,
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.
Sources:
rfc3986 http://tools.ietf.org/html/rfc3986
http://en.wikipedia.org/wiki/Percent-encoding
--
Arno Garrels
--
To uns
12 matches
Mail list logo
