Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81780 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53047 invoked from network); 4 Feb 2015 08:22:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2015 08:22:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 74.125.82.171 mail-we0-f171.google.com Received: from [74.125.82.171] ([74.125.82.171:42994] helo=mail-we0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 58/60-49466-5C6D1D45 for ; Wed, 04 Feb 2015 03:22:29 -0500 Received: by mail-we0-f171.google.com with SMTP id k11so281227wes.2 for ; Wed, 04 Feb 2015 00:22:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=2iU6ZPwVmHpcqqouMriP0oyn4xyRvap/tCV9GfctHrk=; b=Czm8JajRoSvGR3eCjOE4su8lzA+kF262pO7u+IkFQX0VQOknIb2pfpHjxs6Sxd9bXx p01HY/nM5XqJNMMvFAVeg+Zgop9mtWQobkWOhzagTb1TyrQBCJHKHLTacpR/KFQPLnWg 8Fff1ykjWyDBafnQpp+BYnuukGpPT+3CssdO5SReCSqicey2oZTd9vzIUH9Lr4+bVKco 7qsOtlkgQdeg5nAsBX5cg/kWCKQGRkXCi8kzR8pRSzBjCyI2LS+qDbMowPaJk4w2e3Rc +COsyL3rsdloWVrd1THWvNS8vbCF4N5og6v8dOLqmz4RLB7F35qpfxi6lg89zQSsJs5Y I0Vg== X-Received: by 10.180.79.233 with SMTP id m9mr44232203wix.15.1423038146040; Wed, 04 Feb 2015 00:22:26 -0800 (PST) Received: from [192.168.2.120] (89-104-28-113.customer.bnet.at. [89.104.28.113]) by mx.google.com with ESMTPSA id ej10sm2113377wib.2.2015.02.04.00.22.24 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 00:22:25 -0800 (PST) Sender: Michael Wallner Message-ID: <54D1D6C0.6070004@php.net> Date: Wed, 04 Feb 2015 09:22:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Stanislav Malyshev , PHP Internals References: <54D1C946.5080804@gmail.com> In-Reply-To: <54D1C946.5080804@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] removing http line folding support? From: mike@php.net (Michael Wallner) On 04/02/15 08:24, Stanislav Malyshev wrote: > Hi! > > Our header() function supports multiline HTTP headers, which are allowed > by RFC 2616. However, newer RFC - > https://tools.ietf.org/html/rfc7230#section-3.2.4 - deprecates them and > says: > > Historically, HTTP header field values could be extended over > multiple lines by preceding each extra line with at least one space > or horizontal tab (obs-fold). This specification deprecates such > line folding except within the message/http media type > (Section 8.3.1). A sender MUST NOT generate a message that includes > line folding (i.e., that has any field-value that contains a match to > the obs-fold rule) unless the message is intended for packaging > within the message/http media type. > > So, my question is - any objections for dropping this functionality? I'd > be inclined to drop it in all versions from 5.4 up since it may still be > confusing some not too smart clients that don't implement full spec, and > frankly to me it doesn't seem of any use anyhow, but if you disagree, > please explain. > Don't we prevent that already? http://lxr.php.net/xref/PHP_5_6/main/SAPI.c#749 -- Regards, Mike