From 228bb9e7ff517257e170bdeb332dc3f8cf65edd5 Mon Sep 17 00:00:00 2001 From: Rasmus Lerdorf Date: Mon, 30 Oct 2006 17:11:02 +0000 Subject: [PATCH] Pierre requested an update to this. I don't think it makes sense to remove what little API docs we have here, and the simple example in this doc is a lot easier to follow than ext/filter. --- README.input_filter | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.input_filter b/README.input_filter index f55a1eb69da..8fb8244bd82 100644 --- a/README.input_filter +++ b/README.input_filter @@ -10,7 +10,10 @@ The Input Filter support in PHP 5 is aimed at providing the framework through which a company-wide or site-wide security policy can be enforced. It is implemented as a SAPI hook and is called from the treat_data and post handler functions. To implement your own security -policy you will need to write a standard PHP extension. +policy you will need to write a standard PHP extension. There is also +a powerful standard implementation in ext/filter that should suit most +peoples' needs. However, if you want to implement your own security +policy, read on. A simple implementation might look like the following. This stores the original raw user data and adds a my_get_raw() function while the normal