Re: Re: PHP taint support: first results

From: Date: Fri, 05 Oct 2007 18:39:25 +0000
Subject: Re: Re: PHP taint support: first results
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-32658@lists.php.net to get a copy of this message
Rasmus Lerdorf: > Wietse Venema wrote: > > Rasmus Lerdorf: > >> Consider very common (abbreviated) code like this: > >> > >> $user_data = $_REQUEST['data']; > >> switch($output_format) { > > > > Question: where is the output format feature documented? > > > > Once I know the output format is not HTML, then I know > > that applying HTML-style restrictions is not appropriate. > > > > I did search around but came up empty handed. > > That's just an example. People building REST-based web services will > typically include an output format parameter. Or they determine the > output format based on other criteria. It's completely up to the script > author which output format he wants to use and how he wants to make that > decision. Would perhaps the Content-Type: information be stored somewhere in HTTP response, or is this hopeless because of multi-part documents? If Content-Type: header information were available, then I could use that to choose the proper rule. As I mentioned, I don't want to get involved with guessing games. Wietse

« previous php.internals (#32658) next »