Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81776
Return-Path: <smalyshev@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 44877 invoked from network); 4 Feb 2015 07:25:10 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 4 Feb 2015 07:25:10 -0000
Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.43 as permitted sender)
X-PHP-List-Original-Sender: smalyshev@gmail.com
X-Host-Fingerprint: 209.85.220.43 mail-pa0-f43.google.com  
Received: from [209.85.220.43] ([209.85.220.43:46091] helo=mail-pa0-f43.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 5D/B7-20608-359C1D45 for <internals@lists.php.net>; Wed, 04 Feb 2015 02:25:07 -0500
Received: by mail-pa0-f43.google.com with SMTP id eu11so138682pac.2
        for <internals@lists.php.net>; Tue, 03 Feb 2015 23:25:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        bh=1W/iUUclbs4+TB47wfAEyezAHtFVXw7ogR+pnBm6veo=;
        b=F/o73WhhgCn8C5dEpzS/i1VHAZFfT1UL/esZ0M2CXe+e2PI2Ky4gacA76A+EU6SVjs
         rdlbEVW2u0DDm2yK3XHnEcQw48yZZQl15MiwDeF5eJpFelXrfsR1YR0dNaW1LWaaBnd1
         EpOSrpsgsRukrDTI6cqc8pxJaaSKSaIpnYZYKM63yYqaeV1FZ/wcpw5ccQ1DISga7WCB
         4G4zz7So0c9YdglZs4Qq2J8QGJJPaq7cJylQUCXOhSQYLJfF7777jNk3c7o9uemU7y2e
         9Fo+s5ELXIL7Chd0aPvHKmLco/7VMP2XOo7bL3ZNSsJaOxOYXZpTjALWNNi229xOFAMS
         TZhg==
X-Received: by 10.68.69.69 with SMTP id c5mr44599858pbu.90.1423034704753;
        Tue, 03 Feb 2015 23:25:04 -0800 (PST)
Received: from [192.168.2.145] (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48])
        by mx.google.com with ESMTPSA id r14sm980551pdi.67.2015.02.03.23.25.03
        for <internals@lists.php.net>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 03 Feb 2015 23:25:04 -0800 (PST)
Message-ID: <54D1C946.5080804@gmail.com>
Date: Tue, 03 Feb 2015 23:24:54 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: removing http line folding support?
From: smalyshev@gmail.com (Stanislav Malyshev)

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.
-- 
Stas Malyshev
smalyshev@gmail.com