Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117362 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 76455 invoked from network); 17 Mar 2022 16:50:25 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Mar 2022 16:50:25 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2B4FD1804B3 for ; Thu, 17 Mar 2022 11:15:42 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 176.9.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 17 Mar 2022 11:15:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1647540939; bh=+H2rjZ2Fa4cZOU1VBz+gAj+SYQAxfV6HXFm2lXb6E0Y=; h=Date:Subject:To:References:From:In-Reply-To:From; b=TWBOdNh0vzt6Kq8WSy7hBms8ozH+XjcI22fky8lOqn1x6CPw2gSvHlvAo0FFnf4Ih eTbB1x7Fupg0JyT0keoqGl56/uwq3vu02b3sO5XxaL+lGIaCUYfm8q9Oiv8ha3ry1D +1ad18GH5lU8K5A/WwTYXTM3tesO4T1Yp0qkOXF/4RHzewMTnFnref1NqdzVPu47p4 ds61Cg/JRkZZjI0ioHGvuZALQ21vGok7vYn8m7er/dLoY3GtvbBizsR8RCMx2xQlNn rrIzg7/v0QaqcI+zS+E6FjEbJsyp+ESrs1NQCL7v5rP2KfsuCb9wBBxHQ6mSiuPO7d hTlISRBe7Bwgw== Message-ID: <196928ed-2b1a-beaa-b29e-e159f33f6158@bastelstu.be> Date: Thu, 17 Mar 2022 19:15:38 +0100 MIME-Version: 1.0 Content-Language: en-US To: =?UTF-8?Q?Vedran_Mileti=c4=87?= , PHP internals References: <8546c37a-c75b-8130-819b-dcd86df4fbd8@miletic.net> In-Reply-To: <8546c37a-c75b-8130-819b-dcd86df4fbd8@miletic.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Capitalization of Content-* headers From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=) Hi Vedran, On 3/17/22 19:03, Vedran Miletić via internals wrote: > What do you think about this change? > *If* a change is made I'd rather like to see all-lowercase headers, as that's the casing enforced by HTTP/2 [1] [2]. I don't see a benefit in changing one capitalized version to different capitalized version. Even though headers are defined to be case-insensitive there are consumers that (wrongly) rely on a specific casing and thus it as a matter of fact it will be a breaking change to them (even if they are wrong). Best regards Tim Düsterhus [1] https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2 [2] In the (PHP) code I'm maintaining I'm defining any new header in full lowercase.