Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111236 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26513 invoked from network); 28 Jul 2020 21:52:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Jul 2020 21:52:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A58EA180531 for ; Tue, 28 Jul 2020 13:48:48 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 28 Jul 2020 13:48:48 -0700 (PDT) Received: by mail-wr1-f47.google.com with SMTP id a14so19579225wra.5 for ; Tue, 28 Jul 2020 13:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=xenfPudLVei+7UnY9hpvWtb/JTfjfY/cEYCBxxZici4=; b=GyVoYcJEoggEuELY5yOqx1Zz/E+9YE4WAucnUE2avoF+71hkB3HjLaOa9D9h/3UEib EezPCxnGmkECWE5HVIasSm5dEySSn9C3bff//ET/V+OAx0oN6c5tgxNBwSE43W4Htq7Q /+UsiWheZAcvUybYpErz0WmN1xyHLk2OXp7LZWe1gs3EK7RM+3YvJ1c2tYt5z4MgILDI 0PFR++IsI2zWhv0ov73EGWU+3hpKaVCPZ7Sg4h/6AcwGdjuzSZF5RwJc6xWCYeELP2NQ kSSu7E90PGVwqYzMvMEGShoUXB4wVBoLNB6Hnv5zePEtA3Z+Vfi/9prWr2k8vSR+7WUc NbAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=xenfPudLVei+7UnY9hpvWtb/JTfjfY/cEYCBxxZici4=; b=DcYfhoFg+kfn5wiMkXPPKXw18bwoQi7gHuS1vVaZuilKE8bjRXXvom5QNjJXd84oPz cyz2/yj1jo5Fx3LInwmVXquez573Yw7n4uiIH8pyAlfBZUURZqc9ZWJ0NiHtUgOOkQC7 7GbZ6b5a+8cMWcLgu++b1jrtotyAwiuZKFos/AbsjhZ51lDVlo2A8CYj/ironCgo5PCa tKurixZ1riLZz2XwxjO46EJBWG3Guwjf9OTlPR7OPMgwe/1orkD/uXqS9+xbOCqlBnUe JzWgl1GnMvXdIryEAG04zxklcyfITk4OR7gzebEFH8y+1P6luCwaWGx/uurU4CBpFV9H VqUg== X-Gm-Message-State: AOAM533PtuutmYZs1hE1//3N+yWc9ztwrNsDdq1wpmC9GlfUO5P8QNcA 3Ym3gQT+M9m7A6xtbb+qIqZMRs7A X-Google-Smtp-Source: ABdhPJyRPXda52eadfekf10s1VuXZcCUm8KIWFtoNTTSkmRgZswGjUHvye3XyaI093jAMmcxny3wCg== X-Received: by 2002:adf:9404:: with SMTP id 4mr25774556wrq.367.1595969323002; Tue, 28 Jul 2020 13:48:43 -0700 (PDT) Received: from [192.168.0.22] (cpc84253-brig22-2-0-cust114.3-3.cable.virginm.net. [81.108.141.115]) by smtp.googlemail.com with ESMTPSA id f9sm19512839wru.47.2020.07.28.13.48.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Jul 2020 13:48:42 -0700 (PDT) To: PHP Internals References: <9d28ade6-1a70-9850-3bc0-64050c0dcbe4@gmail.com> Message-ID: <290b32e6-e2a0-91e5-1a75-e8d06c8669c4@gmail.com> Date: Tue, 28 Jul 2020 21:48:39 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB Subject: Re: [PHP-DEV] Re: HTTP/1.1 by default in PHP 8.0 From: rowan.collins@gmail.com (Rowan Tommins) On 28/07/2020 19:22, Niklas Keller wrote: > > Do we handle 1XX responses, yet? > https://tools.ietf.org/html/rfc7231#section-6.2 Yes, as of this patch a few years back: https://github.com/php/php-src/pull/2175/files > This is what implementations should do, see > https://tools.ietf.org/html/rfc7230#section-2.6 I guess that's part of the "generous in what you accept" philosophy, since it makes no sense for a server to send a response chunked if the client didn't advertise 1.1 capabilities. > That section also says we should send 1.1, as we support it. Indeed, as far as I have been able to tell, the client code now complies with the spec for HTTP 1.1, although I struggled to find a list of minimum capabilities. Regards, -- Rowan Tommins (né Collins) [IMSoP]