Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81785 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61038 invoked from network); 4 Feb 2015 09:01:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2015 09:01:57 -0000 Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender) X-PHP-List-Original-Sender: php@beccati.com X-Host-Fingerprint: 176.9.114.167 spritz.beccati.com Received: from [176.9.114.167] ([176.9.114.167:34592] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F6/21-55046-FFFD1D45 for ; Wed, 04 Feb 2015 04:01:56 -0500 Received: (qmail 22033 invoked from network); 4 Feb 2015 09:01:48 -0000 Received: from home.beccati.com (HELO ?192.168.1.202?) (88.149.176.119) by mail.beccati.com with SMTP; 4 Feb 2015 09:01:48 -0000 Message-ID: <54D1DFF6.1050301@beccati.com> Date: Wed, 04 Feb 2015 10:01:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Stanislav Malyshev , Michael Wallner , PHP Internals References: <54D1C946.5080804@gmail.com> <54D1D6C0.6070004@php.net> <54D1DDE9.5040307@gmail.com> In-Reply-To: <54D1DDE9.5040307@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] removing http line folding support? From: php@beccati.com (Matteo Beccati) On 04/02/2015 09:52, Stanislav Malyshev wrote: > Hi! > >> Don't we prevent that already? >> http://lxr.php.net/xref/PHP_5_6/main/SAPI.c#749 > > I'm not sure what you meant by "that", but the code you linked to allows > multi-line headers according to RFC 2616 - this is what comment in line > 750 means. I propose to remove this (of course, no newline chars will be > allowed too as they are allowed only to support RFC 2616). How about replacing \r and \n with spaces and throwing E_DEPRECATED instead? Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/