Re: RFC: Implementing a core anti-XSS escaping class
| From: | Anthony Ferrara | Date: | Tue, 18 Sep 2012 16:56:03 +0000 |
| Subject: | Re: RFC: Implementing a core anti-XSS escaping class | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63070@lists.php.net to get a copy of this message | ||
Stas,
On Tue, Sep 18, 2012 at 12:51 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
> Hi!
>
> > I've written an RFC for PHP over at: Śb7S
> > Ø{#|łč¾éPVhttps://wiki.php.net/rfc/escaper.
> > The RFC is a proposal to implement a standardised means of escaping
> > data which is being output into XML/HTML.
>
> We already have filter extension. Is it really necessary to invent yet
> another way of filtering data?
>
Filtering is very different from escaping. They each handle similar but
unique problems:
http://stackoverflow.com/questions/4218136/is-filter-input-escape-output-still-valid-with-pdo/4218219#4218219
> Also, a problem with putting code of this complexity in core would be
> that if it every had a defect - e.g. we forgot to account for some weird
> browser quirk that does not follow RFCs, or some strange encoding
> combination, or just a plain bug - it would be very hard for the users
> to mitigate without upgrading PHP - which is not always under their
> control. When using PHP code, they could just d/l new ZF class, but with
> core implementation it'd be much harder.
>
> So far I am not convinced we should really do it. But if somebody
> creates PECL extension and it proves popular, it may be merged into core
> once it does.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>