Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.php Subject: Re: PHP processing steps to apply to a URL to make it safe Date: Thu, 18 Feb 2016 15:44:16 +0100 Lines: 38 Message-ID: <56C5D8C0.7030703@arnowelzel.de> References: <56C445F6.1090008@arnowelzel.de> <3115586.UhRzssAi4L@PointedEars.de> <56C56D36.2060805@arnowelzel.de> <180220160959369722%timstreater@greenbee.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: individual.net BvlCD82/zkQb/w73fEBlmAIGiFrB7KeuAydAIJuuiyalPVvPAJ Cancel-Lock: sha1:cmHCiKL3Ce9GVYuo5DdIzt1YHGs= In-Reply-To: <180220160959369722%timstreater@greenbee.net> Xref: csiph.com comp.lang.php:16498 Tim Streater schrieb am 2016-02-18 um 10:59: > In article <56C56D36.2060805@arnowelzel.de>, Arno Welzel > wrote: > >> 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: >>>>> >>>>> >>>> >>>> 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 ;-) > > Yes it does. Look at the top of the old RFC (assuming you didn't > download it on stone tablets in AD 54) and it will have an "Obsoleted > by:" line indicating which RFC replaces it. I stand corrected - of course there is an indication. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de