Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.lang.php
Subject: Re: PHP processing steps to apply to a URL to make it safe
Date: Thu, 18 Feb 2016 08:05:26 +0100
Lines: 30
Message-ID: <56C56D36.2060805@arnowelzel.de>
References: <na1es3$rsd$1@dont-email.me> <56C445F6.1090008@arnowelzel.de> <na220i$27e$1@dont-email.me> <3115586.UhRzssAi4L@PointedEars.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 2ruR2IxrwAx0wZ9JZ7g4uglK13tGaHZPzizSCGBHBc+o7yLSqU
Cancel-Lock: sha1:TGFj9U7qvAwthIY2B1JeUzI9PNI=
In-Reply-To: <3115586.UhRzssAi4L@PointedEars.de>
Xref: csiph.com comp.lang.php:16490

Thomas 'PointedEars' Lahn schrieb am 2016-02-17 um 23:33:
> James Harris wrote:
> 
>> On 17/02/2016 10:05, Arno Welzel wrote:
>>> James Harris schrieb am 2016-02-17 um 10:37:
[...]
>>>> In addition to the above, could the URL be in Unicode form? I was
>>>> thinking to change to index through it with
>>>
>>> See RFC 1808:
>>>
>>> <https://tools.ietf.org/html/rfc1808>
>>
>> I looked through it but could not see anything about Unicode.
> 
> It has been obsoleted by RFC 3986 eleven(!) years ago now, which contains 
> something about Unicode, in particular it defines UTF-8 percent-encoding.

That's the problem with RFCs - nothing in the old RFC indicates the
replacement ;-)

But thanks for the hint.



-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de