Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!newsfeed0.kamp.net!newsfeed.kamp.net!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: Wed, 17 Feb 2016 15:04:53 +0100
Lines: 17
Message-ID: <56C47E05.10508@arnowelzel.de>
References: <na1es3$rsd$1@dont-email.me> <na1rs4$9tp$1@jstuckle.eternal-september.org> <56c47913$0$24153$e4fe514c@news.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
X-Trace: individual.net DhE2clm9eTEdBPACpZ04TwU0rgPQ9pluuqrFeaMYkzxXJAT8Zw
Cancel-Lock: sha1:PypRLA7mEfkGTIDoCqiGDTxWN/0=
In-Reply-To: <56c47913$0$24153$e4fe514c@news.xs4all.nl>
Xref: csiph.com comp.lang.php:16445

R.Wieser schrieb am 2016-02-17 um 14:43:

> Jerry,
> 
>> What are you trying to "make safe"?  A url is either good or bad.
> 
> I've got a name for you: "Bobby Tables".  Google it. And XKCD has got a page
> about him: https://xkcd.com/327/

And what do SQL injections have to do with "safe URL"?


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