Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111205 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41410 invoked from network); 28 Jul 2020 00:29:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Jul 2020 00:29:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5FB0E1804D0 for ; Mon, 27 Jul 2020 16:24:57 -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=1.4 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (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 ; Mon, 27 Jul 2020 16:24:56 -0700 (PDT) Received: by mail-lj1-f175.google.com with SMTP id 185so8897085ljj.7 for ; Mon, 27 Jul 2020 16:24:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/pYgk2FD/x0r1fPmjABXUHNHl0AtPVlmSw6q7+CKlC8=; b=tnPdna59alfhXzIoCXvLvvcl93+5I+EcKcTO4kCih686vbfeO8MAFbiYAuHuXZG8oq PnovixgQ/bKpTnrI//hJ4Wc7pUMaqaQwzLnIop+pVIOujxc2oeTSB7+MvhzOZY+na9LF FkZM1860VlvuDP7el8i+cX17rG2w1QhD2VZG3275wrmQ7YQD1e5664An/AJn7DQu+ZCY PbC0c/wPsQv9l5NJQehu/lnzqIOZdCrosRI41PapiRbf8VUDmT/dPzuTDttUJOJMg2Pm MTdjvgM7FmbXegRkUyhqZPynAy271+GbWxCZYbQVNNwY8vq+2YcZtEfHf9oBoWuHPMXp oU9Q== X-Gm-Message-State: AOAM532lRQdEwRNItv9amnnxUlcuAyH6DAtSVpSkkMq4pcJeJVD/bkDB kDp0LVdTSmlbTIaRTZ+Xl1/UGEyhB5aB9elclthZQQ== X-Google-Smtp-Source: ABdhPJyC1AOjT7bR2r5UaAt8LHkV5Tba1sOJ095PRYfqtIK3ax5nvEbB8t7faJwiCFELyd3RLcye2Oc3cJG3eTvMbAY= X-Received: by 2002:a2e:5802:: with SMTP id m2mr10903925ljb.289.1595892291279; Mon, 27 Jul 2020 16:24:51 -0700 (PDT) MIME-Version: 1.0 References: <9d28ade6-1a70-9850-3bc0-64050c0dcbe4@gmail.com> In-Reply-To: <9d28ade6-1a70-9850-3bc0-64050c0dcbe4@gmail.com> Date: Mon, 27 Jul 2020 18:24:40 -0500 Message-ID: To: Rowan Tommins Cc: PHP Internals Content-Type: multipart/alternative; boundary="0000000000001f59b505ab74a1e6" Subject: Re: [PHP-DEV] Re: HTTP/1.1 by default in PHP 8.0 From: pollita@php.net (Sara Golemon) --0000000000001f59b505ab74a1e6 Content-Type: text/plain; charset="UTF-8" On Mon, Jul 27, 2020 at 5:25 PM Rowan Tommins wrote: > A couple of months ago I revived my suggestion to make stream wrappers > advertise HTTP/1.1 by default (full message below), and then Real Life > intervened and I didn't raise the PR. > > The implementation (which is a one-character change) is now here: > https://github.com/php/php-src/pull/5899 > > I realise it's now rather last-minute for 8.0, so if anyone thinks it > should have more careful thought, or an RFC, it will have to wait. If > there are no objections, though, it would be nice to have it merged > before the freeze. > > Given that it's a very small change, the RFC is probably not necessary, in which case it's not too late, however I'd like some clarification about what this actually offers over defaulting to 1.0. Specifically, are there known servers which will refuse to serve 1.0 clients? Script authors have had the option of opting into 1.1 for some significant time now. Basically, what's the chance of something accidentally not working due to advertising 1.0 versus something not working due to advertising 1.1? If the changes are equal, I'd *personally* err in favor of status quo since those needing 1.1 have already opted into it, those needing 1.0 may not have. -Sara --0000000000001f59b505ab74a1e6--